Is Next.js still the King?
Is Next.js still the King?
Back in 2023, Next.js was the undisputed default for anyone building a React app. Fast forward to 2026, and while it's still the biggest player, the "Vercel way" isn't the only way anymore. I've spent the last few months jumping between frameworks, and the landscape has shifted from "features at any cost" to "performance through simplicity."
The Server Component fatigue
React Server Components (RSC) were supposed to be the holy grail. In theory, they're amazing, zero-bundle-size components that fetch data on the server. In practice, the mental overhead of managing the boundary between 'use client' and server code has pushed many developers away.
I've seen teams migrate back to simpler architectures because they spent more time fighting with serialization errors than building features.
The rise of the "Lightweight" stack
We're seeing a massive surge in tools like Hono and Remix.
- Hono: It's incredibly fast and runs on anything (Bun, Deno, Cloudflare Workers). It feels like what Express should have evolved into.
- Remix: Now that it's being merged into the core of React Router, it has become the go-to for developers who want a stable, standards-based framework without the complex caching layers of Next.js.
What actually matters in 2026
If you're starting a project today, don't just pick Next.js because of the hype. Consider these three things:
- Deployment Flexibility: Can you move your app off Vercel without a total rewrite? If the answer is no, you're dealing with vendor lock-in.
- Type Safety: If you aren't using something like tRPC or Prisma/Drizzle, you're working harder than you need to. End-to-end type safety is no longer optional.
- The "Boring" Choice: Sometimes, a Vite-based SPA with a separate Go or Node backend is better than a complex meta-framework. It's easier to test, easier to scale, and easier to hire for.
"The best framework is the one that lets you ship your idea before you get bored of the setup."
“
Next.js is still powerful, especially for high-traffic content sites. But for internal tools or lean startups, the "lightweight" movement is winning. We're finally valuing developer experience over framework-specific features again.