I agree, and it feels like JS is just the wrong runtime for agents. Really languages that can model state in sane ways and have a good concurrency story like Elixir make much more sense.
And here’s a fun exercise: ask Claude via Cursor or Perplexity with R1 to create a basic agentic framework for you in your language of choice on top of Instructor.
Call me an elixir virgin until 5 minutes ago. This language from a quick glance seems perfect for agent orchestration.
Project looks great, will follow & learn.
> Really languages that can model state in sane ways and have a good concurrency story like Elixir make much more sense.
It has concurrency with Promise; it doesn't have parallelism.
And these agents are all network I/O bound by the model services so a lot of use cases don't need threading.
I would argue that python is the overrated language when it comes to building agents. Just because it's the language of choice for training models doesn't mean it should be for building apps against them.
The dx typescript brings to these types of applications is nice.
> The dx typescript brings to these types of applications is nice.
What I've found is that teams that want TS probably should just move up to C#; they are close enough [0]. The main thing is that once you start to get serious with your backend API, then data integrity matters. TS types disappear at runtime and it's just JS. So you need a Zod or Valibot to validate the incoming data. Then your API starts getting bigger and you want to generate OpenAPI for your frontend. Now your fast and easy Node/Express app is looking a lot like Spring or .NET...without the headway and perf...the irony.
> good concurrency story like Elixir make much more sense
Agree, that's why I've been building this: https://github.com/agentjido/jido