Next.js
Reddit take
AI summary of the Reddit excerpts below — not a quote
Next.js is a widely adopted React framework that is currently experiencing significant developer pushback due to its perceived complexity and "bloat." While it is praised for its Server-Side Rendering (SSR) benefits and ability to achieve high performance scores, many users find the mental overhead of its architecture—specifically the distinction between client and server components—to be a major drawback. Sentiment is currently leaning negative, with frequent complaints regarding its suitability as a backend and a tedious local development experience.
Pros
- Excellent SSR benefits leading to better first-page load experiences
- High industry adoption and strong demand in the job market
- Capable of achieving 100 Lighthouse performance scores
- Includes helpful defaults like Tailwind CSS in the standard setup
Cons
- High mental overhead required to manage client vs. server components
- Perceived as a weak or "frontend-style" backend for complex applications
- Tedious and difficult local debugging process
- Frequent reports of increasing complexity and architectural bloat
- History of security vulnerabilities requiring version upgrades
Caveats
- Maintaining high performance requires significant context and knowledge, making onboarding difficult
- Folder-based API routing can become unmanageable as project scope grows
- Users report a strong sense of vendor lock-in with the Vercel platform
Best for
- Projects where SEO and initial page load speed are top priorities
- Simple sites like portfolios or basic dashboards
- Developers looking to learn the most popular framework for job market readiness
Avoid if
- You need a production-grade, robust backend for complex logic
- You prefer the simplicity of standard React with Vite and React Query
- You want to avoid the complexity of managing server-side and client-side execution contexts
This summary uses balanced time weighting with about a 6-month half-life. The evidence is older (median age ~283 days), and since Next.js is a fast-changing software tool, confidence is medium as some mentions may refer to older versions or specific CVEs that have since been patched.
Sentiment
9 positive (24%) · 7 mixed (19%) · 21 negative (57%)
Trust + time weighted score: -32% · raw score -32%
What redditors said (10 of 37)
Performance feels great! I’m currently using Next.js and Vercel for https://sedna.sh/, and despite the 100 lighthouse score I will say - the amount of context and knowledge I need to have to keep it that way makes me very nervous at the prospect of onboarding others onto the project. :/
The typical case is the devs have a deep knowledge of nextjs or something but have literally never been trained in basic usability or graphic design concepts.
Next.js is trash, it used to be simpler before.
Vercel send out an email warning of vulnerabilities in Next.js a couple of days ago. I’m not sure it’s this one, but it should be fixed from version 15 and onwards.
It's a production grade rendering service, it is not a production grade backend IMO.
Next.js sucks as a backend unless you're doing something incredibly basic like a portfolio site with a couple API requests.
Next.js backend is a frontend dev's idea of backend
It sounds like it solves a bunch of "problems" like only loading what you need, seamless server/client integration, etc.. None of these were actual problems in practice, and the "solutions" came with a very steep cost.
I tried it and tapped out when I realised how tedious it was to debug locally (please don't reply challenging this). I don't understand how anyone is actually productive using it.
as much as I'd like to hate on nextjs, you cant just pretend that it doesnt offer a lot of ssr benefits
Compare
Related
- Proxmox · related · 107 mentions
- Visual Studio Code · related · 87 mentions
- React · related · 54 mentions
- OPNsense · related · 27 mentions
- ZFS · related · 23 mentions
- Tailwind CSS · related · 22 mentions