Almost all AI programming tools use React as the standard. This single piece of information will have a greater influence on frontend development in the next ten years than any technological indicator ever will.
Consider this: When a million engineers ask ChatGPT to “create a todo app for me”, they receive React. When somebody uses v0 or Bolt to bootstrap a SaaS dashboard, they get Next.js. React won by being the default.
The Training Data Flywheel
LLMs are only as good as the data they’re trained on. The web contains more React examples than any other code. Thus, LLMs create React examples more proficiently than anything else.
This makes the circle virtually unbreakable. More React results in more React in the training data to follow. More React in the data trains a better React model. A better React model leads to more people producing React. 🔄
→ React dominates training corpora
→ LLMs generate React with higher quality and confidence
→ AI-powered tools choose React as their default
→ New projects ship React, producing more training data
→ The cycle repeats
Svelte and Solid are genuinely excellent. But they have a fraction of the representation in the data that shapes these models. It doesn't matter if your framework is technically superior when the robots haven't read enough of it to be fluent.
Vibe Coding Is a React Monoculture
"Vibe coding" — where you describe what you want and an AI builds it — is exploding. And it's overwhelmingly React.
v0 generates React components. Bolt scaffolds Next.js apps. When non-technical founders prototype their ideas with AI, they're unknowingly casting a vote for React's continued dominance. They don't care about the framework. They care that it works. And React works because the AI knows it best.
This is the worst possible news for framework diversity. Innovation used to spread through blog posts, conference talks, and developer curiosity. Now adoption spreads through whatever the LLM spits out first.
Why This Should Bother You (Even If You Love React)
I don't hate React. It's fine. It does the job. But "fine" shouldn't win by default forever.
Monocultures are fragile. They stifle the experimentation that gave us hooks, signals, compiled reactivity, and server components in the first place. If every new project starts as React because an AI decided, we lose the pressure that forces frameworks to evolve.
The irony is brutal: React's best features were inspired by ideas from smaller frameworks. Signals came from Solid. Compilation came from Svelte. If those frameworks can't gain adoption because LLMs ignore them, React loses its own innovation pipeline. 😬
What Would It Take to Break the Loop?
Honestly? I'm not sure it can be broken organically. A few things that might help:
→ AI tool builders intentionally offering framework choice upfront
→ Smaller frameworks investing heavily in structured training data and documentation
→ A major LLM provider partnering with a non-React framework as a first-class target
But the incentives don't align. Tool builders want reliable output. Reliable output means React. Nobody's going to ship a worse product to promote ecosystem diversity out of principle.
The Uncomfortable Truth
React is unlikely to become obsolete because it's the best tool for the job. It's unlikely to fade out because it has the largest, most engaged community. It's no longer possible to have an alternative perspective because the machines are the ones imposing it on us, and we are increasingly accepting the decisions of the machines.
There’s no conspiracy here, just logic. The amount of data used to train the model has created a force of gravity, and every line of code generated by AI makes it stronger. 🕳️
So the real issue is: if you're starting a new project today and an AI presents you with React —will you take it, or will you resist the current? And if you do choose to resist, why?
Top comments (0)