What the internet is saying about Next.js

What the internet is saying about "Next.js"

🟢 Supporters

• •LLMs recommend it as default stack. An openllmrank.io post titled "Best app stack of 2026, according to LLMs" lists Next.js, Supabase, Vercel, Stripe [8]. It got only 3 points and 0 comments, so this is a weak signal of community enthusiasm [8].
• •Active release cadence. Next.js 16.4 was announced on the official blog [2]. One commenter there prefers the older page router for its simpler caching model, but also values that Next presented a "unified platform" instead of the "fragmented sea of hacks that is web development" [2].
• •Continued use as a build target. Hobby projects such as a GitHub profile stats card are built with it [9]. Appwrite's console PR treats Next.js as a first-class framework with multiple adapters [7]. Next.js's own test suite (e.g., trailingslash) is also used to validate third-party deploy runtimes [5].
• •Ecosystem tooling stays current. Dependency bumps for @sentry/nextjs (11.2.0 → 11.4.0, and the Sentry monorepo update to v11.8.0) show routine maintenance [11][13].

🔴 Skeptics

• •"You don't need it for a static site." The most-discussed item is a post about removing Next.js to reach 100 on every Lighthouse category (198 points, 129 comments) [1]. The top comment says: "They never needed Next.js for a static blog," likening it to bragging about taking the bus instead of a Ferrari [1].
• •React itself questioned. The same commenter argues the "vast majority of websites don't need Next.js or React," and that the default came from "name recognition and simple inertia" [1].
• •Caching and complexity. A commenter on 16.4 "still much, much prefer[s] the page router" because "the caching model is much simpler" [2].
• •Ecosystem and governance complaints. Commenters say that hiring the React maintainers means "nothing other than Tan stack gets developed," and they wish Next would stop being the "darlings extension framework for SaaS vendors in the MACH ecosystem" [2].
• •Security issues. The October security update reportedly fixed two unauthenticated RCEs, with a note to check sharp too [3][4]. A separate writeup, CVE-2026-23870, claims "a single post freezes any Next.js server" via React RSC FormData [6]. These items have little discussion (0 comments each), so the reaction is unclear [3][4][6].

⚪ Neutral Observers

• •Compatibility and adapter work. Appwrite stopped pinning new sites to the static adapter. For frameworks that support multiple adapters, Next.js among them, the adapter is now left empty so the first build detects it [7].
• •Blocked upstream. One SDK samples bump skipped Next.js, along with Astro, Gatsby, NestJS and Nuxt, because no newer publish was available [10].
• •Framework comparisons. A docs issue plans a Web Frameworks and CMS comparison page covering popularity, performance, cost and security [25].
• •Noise. Many Polymarket results ("Next Prime Minister of Spain," "Next James Bond actor," etc.) only match the word "Next" and are unrelated to Next.js [14]–[24]. Several large GitHub agent-coordination issues are also tangential [26]–[29].

Cross-Platform Signals

• •Hacker News carries the real debate: the Lighthouse/static-blog thread, the 16.4 release thread, and three security items [1][2][3][4][6].
• •GitHub shows Next.js as infrastructure, appearing in dependency bumps, deploy adapters and runtime compatibility tests rather than in opinion [5][7][11][13].
• •Polymarket has no relevant Next.js markets in this data [14]–[24].
• •Consensus and divergence: Usage looks entrenched on GitHub, while HN sentiment is more critical, focusing on over-use, caching complexity and security.

Community Verdict

Next.js remains a default, deeply embedded part of the web ecosystem, with ongoing releases (16.4) and tooling support, and even LLMs recommend it [2][8][11]. The loudest discussion, though, is skeptical. Developers argue it is overkill for simple or static sites, that the caching model is too complex, and that the project is too tied to Vercel-style vendor ecosystems [1][2]. October security disclosures, including reported unauthenticated RCEs and a DoS CVE, add concern, although they drew little discussion [3][4][6]. Overall sentiment: widely used but increasingly questioned, with "right tool for the job" as the recurring theme.

---

Based on Hacker News + GitHub + Polymarket data from the last 30 days, researched with last30days by Matt Van Horn.