Next.js 16.2
goldkey
14 points
1 comment
March 18, 2026
Related Discussions
Found 5 related stories in 94.1ms across 8,303 title embeddings via pgvector HNSW
- Next.js Across Platforms: Adapters, OpenNext, and Our Commitments makepanic · 14 pts · March 26, 2026 · 60% similar
- Node.js 26.0.0 (Now with Temporal) aarestad · 129 pts · May 20, 2026 · 53% similar
- TanStack Start Now Support React Server Components polywock · 84 pts · April 14, 2026 · 53% similar
- We moved Railway's frontend off Next.js. Builds went from 10+ mins to under 2 bundie · 200 pts · April 08, 2026 · 51% similar
- Staged publishing and new install-time controls for npm brianmcnulty · 36 pts · May 22, 2026 · 50% similar
Discussion Highlights (1 comments)
dzonga
You've to admire Next.js for bringing sanity to the JS (React) ecosystem by having one encompassing framework Also admire them for their Fire & Motion strategy (people always fixing their next.js apps whether its app router or whatever happens there). Their brilliant marketing that a generation of devs believe deploying means deploying on Vercel and not being aware that Vercel runs on AWS. However the tragedy is we've a generation of dev's who don't know actual sanity i.e proper web frameworks that are full-stack such as Rails & Django. Those dev's have accepted complexity as Dogma A.I doesn't help - since its trained on Nextjs apps - so as A.I churns more apps they're most likely Next.js apps hence they're senior dev's who are incapacitated but don't know it. to me that's the greatest tragedy in all of this.