13
dead framework theory
aifoc.usThese are my opinions and are ruminations on what might be happening as more and more developers use LLMs and Frameworks to build on the web.
In October last year I wrote “will developers care about frameworks in the future?” predicting that LLMs would abstract away framework choice. I was wrong—or at least, wrong about the timeline.
The reality is more interesting and more permanent: React isn’t competing with other frameworks anymore. React has become the platform. And if you’re building a new framework, library or browser feature today, you need to understand that you’re not just competing with React—you’re competing against a self-reinforcing feedback loop between LLM training data, system prompts, and developer output that makes displacing React functionally impossible.
I will argue for standardization/normalization here though. If the change isn’t significant enough or fundamentally needed to achieve something that need or REALLY want, why does it matter if it does catch on?
Like I would rather people make 100 useful things, than polish/refactor/tweak things a 100 times causing everyone to have to learn a 100 new UX changes (yes we are users of the frameworks and languages, though are just different UIs and how we use it is our UX)