What the internet is saying about Next.js

What the internet is saying about "Next.js"

🟢 Supporters

• •Direct praise is thin in this data. The clearest pro-Next.js sentiment is a commenter on the 16.4 release thread who says "One of the things I liked about Next is that it presented a 'unified platform' instead of the fragmented sea of hacks that is web development." [2]
• •The same thread includes a preference for the Pages Router: "I still much, much prefer the page router. The caching model is much simpler." [2] This is a complaint about the newer direction, but it shows continued attachment to part of Next.js.
• •Adoption signals are strong in GitHub dependency PRs, which show projects actively upgrading, for example next from 14.2.20 to 16.4.3 [6] and support for 16.4.5 [3].
• •Hacker News users are still building small projects on it, such as a GitHub profile stats card generator [9].
• •Appwrite's console change lists Next.js among frameworks that support multiple deployment adapters, so it remains a first-class deploy target [8].

🔴 Skeptics

• •The most-engaged item (198 points, 133 comments) is a post titled "Removing Next.js Got My Blog to 100 on Every Lighthouse Category" [1]. A top commenter says: "They never needed Next.js for a static blog… The vast majority of websites don't need Next.js or React." [1]
• •The same commenter says React is "not a good framework for websites in general" and that its popularity comes from "name recognition and simple inertia." [1]
• •On the 16.4 thread, a commenter complains that Vercel "hired all the open source react maintainers and now nothing other than Tan stack gets developed." They also resent Next.js being the "darlings extension framework for SaaS vendors in the MACH ecosystem." [2]
• •Security is a recurring concern:
  • •CVE-2026-23870 is described as "A Single Post Freezes Any Next.js Server" [7].
  • •An October update reportedly fixed two unauthenticated RCEs, with a note to "check sharp too" [5].
  • •A separate upstream-vulnerabilities update was published [4].
  • •The November release (16.4.5) fixes seven advisories [3].

⚪ Neutral Observers

• •Next.js 16.4 shipped in October [2], followed by 16.4.5 as the "November 2026 security release" [3]. The release cadence is fast.
• •Dependency bumps show real-world upgrade friction and coupling. For example, next and @sentry/nextjs must be updated together [6].
• •One commenter suggests porting Next.js to Rust ("Next.rs") [2]. This is a speculative idea, not a signal of any plan.
• •Several Polymarket results (Prime Minister of Israel, Spain, Serbia, Sweden, and others [10]–[19]) matched only the word "next" and are unrelated to the framework.
• •Many other GitHub items in the results mention Next.js only incidentally or not at all [20]–[40].

Cross-Platform Signals

• •Hacker News carries the substantive discussion: the Lighthouse/"you don't need it" debate [1], the 16.4 release thread [2], and security writeups [4][5][7]. The security posts drew only 0–3 points and no comments, so there is little visible engagement.
• •GitHub shows operational use: version bumps, security-release support PRs, and framework-adapter handling [3][6][8]. This points to continued real-world adoption.
• •Polymarket has no relevant Next.js markets.
• •Divergence: GitHub shows ongoing adoption and upgrades, while Hacker News commentary skews critical of Next.js and React for simple sites.

Community Verdict

Next.js is still widely deployed and actively maintained. The GitHub evidence shows teams upgrading to 16.4.x and adopting security patches [3][6]. Online sentiment on Hacker News is skeptical, though. The criticism is mostly that it is overkill for static sites [1], that the caching model and Vercel's influence are frustrating [2], and that a run of serious vulnerabilities, including RCEs and a denial-of-service issue, is concerning [5][7]. Praise exists but is muted, such as its "unified platform" appeal [2]. The overall mood is "entrenched but scrutinized."

---

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