Discussion

Search code, repositories, users, issues, pull requests...

petcat: It looks like it's a fork of Django that just kind changed a bunch of stuff arbitrarily?

pbreit: That would be good if the changes are to slim it down by 80%.

awongh: TLDR:- fork of django- it's opinionated- typed- comes with skills / rules / docs baked inI'm not against this idea in principle, but I'm also not sure why that is better than what's already out there, except maybe you save some tokens by not vibe coding this yourself?I do think in the future we'll see some novel libraries that are agent-optimized first. I'm not sure if this is it, though.(edit: formatting)

giancarlostoro: Very likely its being changed by an AI model, driven by human prompts.

SwellJoe: Inventing a new thing "for agents" always feels counter-productive. Your new thing isn't in the training data, so you have to teach it how to use your thing. Why not use tech that's already in the training data? Agents know Python and Django. Or, better (because the performance, maintainability, and deployment story are much nicer with no extra work, since agents write the code), agents know Go.The very nature of LLMs means you can't invent a thing for current agents to use that they'll be better at using than the things they already know how to use from their immense training data. You can give them skills, sure, and that's useful, but it's still not their native tongue.To make a thing that's really for agents, you need to have made a popular thing for humans ten years ago, so there's a shitload of code and documentation for them to train on.