Frameworks function the same in the agentic era as they did prior: as guardrails to prevent people from doing silly things and to keep implementations focused and bounded. Yes, they still matter.

Do they matter? Yes. Should you use them? No. (Mostly)

This is going to be opinionated from an extreme "vibe code" viewpoint, but I think the future is "GAD" Governed Agentic Development. Designing constraints that agents must follow, and therefore different forms of frameworks. What the agents need is lines in a coloring book, the human is responsible for drawing those lines. So frameworks of the future should be focused on constraining an agent to develop properly, or designing what is and is not permitted.

Building Autonomously, Open Source: https://github.com/pullboard-dev/pullboard

There has never been a time to write frameworks that constrain how things have been done.

Almost all of our work is on our framework internally. The latency, guarantees, build time errors, and feedback that can enable vibe coding individual implementations.

I find myself constantly wishing for more framework code; I wish we had built our original framework in something that threw angrily when we abused it more.

I wish our type system were more expressive, I wish our threading story were better, I wish I wish I wish.

It’s never been easier to rework the whole thing, and I still am happiest when our framework is artisanal.