Are you using Next.js or considering it for your next project? 
Then hold up — you need to hear what’s going on in the dev world before you commit. - ⚡ **Blazing-fast performance** 
- 📈…

Nearform

Luca Pagliaro

Ethics

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Developers and companies are increasingly moving away from Next.js due to issues like performance bottlenecks, overengineering, and vendor lock-in with Vercel. While Next.js offers benefits such as fast performance and SEO-friendly architecture, its complexities and limitations have made alternatives like Astro, Remix, and Qwik more appealing. For simpler, faster solutions, some developers are resorting to using React with Vite instead.

Why Companies Are Saying Goodbye to Next.js 🚪💨

The Breaking Point: Real-World Frustration

Finally, we can move on to overcomplicating something else!

I think this post raises some valid points about evolving complexity, but many of the issues mentioned here seem to stem more from individual developer experience than from fundamental flaws in Next.js itself.
I’ve been using Next.js for over two years, building multi-tenant B2C applications in the food delivery space, and I’ve found that most of the so-called “overengineering” becomes an advantage when used properly. Features like the App Router, Middleware, and RSCs might have a learning curve, but they also offer serious flexibility and performance when applied thoughtfully.
Every tool has trade-offs, and of course Next.js isn’t perfect or one-size-fits-all — but generalizing isolated struggles into a blanket “Next.js is broken” narrative doesn’t do the ecosystem justice.
Constructive critiques backed by data and real use cases would be much more helpful for developers trying to make informed decisions. Just my two cents!

I’m tired of next js and react In general
I’ve been enjoying the way svelte 5 does things.

Would be nice to see the data proving these statements. Without them I do not believe you.