← Back to context

Comment by cpursley

3 days ago

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.

> good concurrency story like Elixir make much more sense

Agree, that's why I've been building this: https://github.com/agentjido/jido

  • 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.

    • It's less about the language syntax and more about the capabilities of the underlying Erlang runtime. There's also Gleam on top of Erlang if you like stronger typing (gleam.run).

    > Really languages that can model state in sane ways and have a good concurrency story like Elixir make much more sense.

Can you expand on this? Curious why JS state modelling falls short here and what's wrong with the concurrency model in JS for agents.