Comment by _pdp_

Comment by _pdp_ 2 days ago

I don't want to be that person but there are hundreds of other similar frameworks doing more or less the same thing. Do you know why? Because writing a framework that orchestrates a number of tools with a model is the easy part. In fact, most of the time you don't even need a framework. All of these framework focus on the trivial and you can tell that simply by browsing the examples section.

This is like 5% of the work. The developer needs to fill the other 95% which involves a lot more things that are strictly outside of scope of the framework.

calcsam 2 days ago

Some people don't like frameworks. Some people do. We have a little bit of experience building frameworks, so we figured we'd build a good one.

Reply View 1 reply

santa_boy 2 days ago

I love frameworks :)

Reply View | 0 replies

incanspyder 2 days ago

Couldn't agree more. This also looks mostly like a Typescript "port" of Langgraph, and I say "port" because Langgraph has a TS framework already.

Reply View 0 replies

fsndz 2 days ago

True. That's the reason I see a lot of people dropping similar frameworks like LangChain recently: https://medium.com/thoughts-on-machine-learning/drop-langcha...

Reply View 2 replies

jerrygoyal 2 days ago

i was using vercel ai sdk for my production app and it was such a bad experience that I eventually went with native implementation and tbh it was not much of work thanks to cursor. problems i faced: too many bugs (just browse their github repo to get an idea), the UI side also had suboptimal performance based on how they implemented hooks.

Reply View | 1 reply
- ilrwbwrkhv 2 days ago
  
  vercel's whole shtick is to make money off of dumb js devs who do not know better. i think they pay far too much attention on how things look compared to how things work. but hey, they made millions, possibly billions off of those js devs so who is to blame them.
  
  Reply View | 0 replies

cpursley 2 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.

Reply View 9 replies

mikehostetler 2 days ago

> good concurrency story like Elixir make much more sense
Agree, that's why I've been building this: https://github.com/agentjido/jido

Reply View | 2 replies
- MattDaEskimo 2 days ago
  
  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.
  
  Reply View | 1 reply
  
  cpursley 2 days ago
  
  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).
  
  Reply View | 0 replies
CharlieDigital 2 days ago
> 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.
Reply View | 5 replies
- dartos 2 days ago
  
  For one, NodeJS doesn’t have concurrency. It’s a single threaded event loop.
  
  Reply View | 4 replies
  
  CharlieDigital 2 days ago
  
  It has concurrency with Promise; it doesn't have parallelism.
  
  Reply View | 3 replies

fullstackwife 2 days ago

You could describe all frontend JS frameworks the same way: you spend 95% of time on content and mechanics of your webapp, while the framework provides the easy 5%.

Reply View 1 reply

chipgap98 2 days ago

I think most JS frameworks save more than 5% of the effort for developers compared to writing raw JS. Especially when you include the ecosystem around those frameworks

Reply View | 0 replies