Thanks for the reply! It’s good to hear from someone working on this directly. Unlike you I am not currently working on anything in this area, so I am operating almost entirely on intuition. But with that said I do have some suspicions as to how things will play out, and I’ve voiced some of them already.
I think it’s more important that we provide “building blocks” in Elixir rather than an “agentic framework” per se, since the BEAM itself provides that framework. Not even OTP necessarily, but the scheduler and runtime is just so well-suited to the task IMO. Providing tools for tool calling, monitoring, etc is what will be important. From a cursory look I see Jido is providing some of those things, so I think you’re probably on to something there.
Yeah, I don’t see the value proposition for “swarms of agents” or anything like that (seems almost anthropomorphic tbh). But Elixir is great because it will scale out so well if you deploy a real app with real users.
Of course one can get fantastic value out of this model. The best example would be LiveView, which is “just” a GenServer if you squint and yet provides much more than the sum of its parts in practice.
I think it’s best not to get distracted here. There is a lot of hype nonsense going around (see my above comment about protocols) which is probably not going to stick. The LLMs are the only interesting thing about LLMs (imagine that) - so it’s best to focus on them. APIs will come and go (and can be trivially implemented with Req and so on).
