This is a sharp take—and honestly, pretty accurate—but I’d push it one level deeper.
Meta-frameworks didn’t just “take over frontend”… they redefined what frontend even is.
What you’re really describing is the collapse of boundaries:
frontend vs backend
client vs server
app vs infrastructure
Tools like Next.js or Remix aren’t just giving better defaults—they’re quietly forcing developers to think in systems, not components.
And that’s where many devs actually fall behind.
Because the real skill shift isn’t:
“learn Next.js”
It’s:
understand rendering strategies, data flow, and where code should run
Meta-frameworks hide complexity, but they also demand deeper mental models:
When should something run on the server vs client?
What belongs at the edge?
How do you minimize hydration cost?
What’s the tradeoff between DX and control?
Also worth noting: this “less JS” movement isn’t just about performance—it’s almost philosophical. It’s a return to the web’s original model (documents + server), just upgraded.
One thing I’d challenge slightly:
Meta-frameworks aren’t always the default best choice—they’re the default safe choice. For many apps, especially smaller ones, they can be overkill and introduce unnecessary abstraction.
Big picture:
We’re not moving from React → Next.js.
We’re moving from:
building apps
to:
designing execution environments
That’s the real shift most devs don’t notice