My Experience with Next.js Why It's Bad (And Getting Worse)

For the longest time (since 2021), Next.js has been my go-to framework for working with React. It’s been my default choice, and for good reason, since has had, ✅ Great performance ✅ SEO-friendly ✅ Dev tools and integrations galore ✅ Vercel made deployment a breeze But over time, things started to feel… off. And recently, downright frustrating. Here’s my personal experience with Next.js — what started as admiration gradually turned into a checklist of red flags. 1. Ever Changing Principle Next.js has become increasingly difficult to rely on due to its constantly shifting direction. It started as a champion of Jamstack and static site generation, but over time, pivoted toward serverless architecture and heavily promotes server-side rendering (SSR). Now, they’re moving away from serverless again in favor of microVMs. These changes contradict its original philosophy and result in frequent shifts to the framework’s core foundations—forcing developers to constantly relearn and adapt. 2. From Simple to Spaceship

Apr 13, 2025 - 13:16

My Experience with Next.js Why It's Bad (And Getting Worse)

For the longest time (since 2021), Next.js has been my go-to framework for working with React. It’s been my default choice, and for good reason, since ~~has~~ had,

✅ Great performance

✅ SEO-friendly

✅ Dev tools and integrations galore

✅ Vercel made deployment a breeze

But over time, things started to feel… off. And recently, downright frustrating.

Here’s my personal experience with Next.js — what started as admiration gradually turned into a checklist of red flags.

1. Ever Changing Principle

Next.js has become increasingly difficult to rely on due to its constantly shifting direction. It started as a champion of Jamstack and static site generation, but over time, pivoted toward serverless architecture and heavily promotes server-side rendering (SSR). Now, they’re moving away from serverless again in favor of microVMs.

These changes contradict its original philosophy and result in frequent shifts to the framework’s core foundations—forcing developers to constantly relearn and adapt.