66 engineers on Hacker News describe using Next.js first-hand: 19 endorse it, 21 regret it, 4 are mixed.
“I run a dynamic website on nextjs static export... Blazing fast, no nodejs or SSR in production.”
endorse · production · littlecranky67 · 2026-10-26 · source ↗ · wrong label?“We use nextjs at work and I hate it. Why write each view once when you could write it twice?”
regret · production · post-it · 2026-10-26 · source ↗ · wrong label?“Vercel + Next is cheap if cached correctly.”
endorse · production · lukeigel · 2025-12-21 · source ↗ · wrong label?“the framework matches my mental model of where I want to get very well.”
endorse · production · berekuk · 2025-12-12 · source ↗ · wrong label?“I regret learning the "modern" framework.”
regret · personal · 1 yr · esperent · 2025-12-05 · source ↗ · wrong label?“we switched Levels.fyi from gulp.js to next.js. Our pagespeed, hosting costs, etc all took a significant hit.”
regret · production · Zaheer · 2025-10-30 · source ↗ · wrong label?“Insisting on using it for SSR via Next is self-inflicted pain down the road.”
regret · production · port11 · 2025-10-17 · source ↗ · wrong label?“mostly it's actually been pretty nice. However, the crazy high level of abstraction and black-boxing does mean occasionally we run into bugs”
mixed · production · soiltype · 2025-09-02 · source ↗ · wrong label?“we run Next.JS, don't host on Vercel - and really don't have many problems at all.”
endorse · production · jhaile · 2025-09-02 · source ↗ · wrong label?“Next is such a bizarre black box that things like this were a regular occurrence.”
regret · production · jowday · 2025-06-12 · source ↗ · wrong label?“no Nextjs lock-in, we migrated off Nextjs to Hono and only had to change the router”
regret · production · stevelacy · 2025-05-19 · source ↗ · wrong label?“We've migrated to NextJs App Router where I work. While RSCs introduce a certain level of complexity, we've appreciated their benefits.”
endorse · production · tresil · 2025-01-23 · source ↗ · wrong label?“I had one project that used Next. It was one of the most painful things I've used in my 25 year career.”
regret · production · christophilus · 2025-01-01 · source ↗ · wrong label?“we never had a more relaxed team especially since we ditched nextjs and react”
regret · production · anonzzzies · 2024-12-06 · source ↗ · wrong label?“We ditched react and nextjs(broth of satan himself that it is) mostly (clients we are trying to lose)”
regret · production · anonzzzies · 2024-12-04 · source ↗ · wrong label?“Started on Next.js 12. The DX was overall "janky"... Next.js 13 didn't make things better.”
regret · production · CharlieDigital · 2024-10-10 · source ↗ · wrong label?“For our new project, we decided to try Next.js for the first time and the entire experience has been hell.”
regret · production · theogravity · 2024-10-10 · source ↗ · wrong label?“we moved to Next.js instead -- best technical decision I ever made as a dev.”
endorse · production · solardev · 2024-06-27 · source ↗ · wrong label?“Then we switched to Next, with some "use client" / RSC headaches we moved some heavy computing to provide most of content”
mixed · production · maelito · 2024-01-04 · source ↗ · wrong label?“Eventually we moved to nextjs and vercel. We are faster with iterating on our landing page”
endorse · production · debarshri · 2023-12-30 · source ↗ · wrong label?“We use Next very successfully, and, well it almost became the main way to use React nowadays”
endorse · production · poisonborz · 2023-12-20 · source ↗ · wrong label?“I've used all of them in production on major web apps and they're half baked. I avoid them.”
regret · production · erikpukinskis · 2023-11-11 · source ↗ · wrong label?“The next.js stuff is a horrible nightmare of different errors. Everytime I need to do a one-line change I get to do a nice debugging session.”
regret · personal · jokethrowaway · 2023-11-04 · source ↗ · wrong label?“our current marketing site is NextJS hosted on Hetzner fronted by Cloudflare, fortunately that's still up and never has any problems.”
endorse · production · madjam002 · 2023-10-30 · source ↗ · wrong label?“the web presence team is happy with Next and Vercel, but beyond modest scale running Next yourself needs a lot of effort.”
mixed · production · jitl · 2023-10-28 · source ↗ · wrong label?“Next is headed that way, but it still doesn't handle some things out of the box (like redux toolkit fetch and slice stuff).”
mixed · personal · solardev · 2023-09-24 · source ↗ · wrong label?“Just after using it for two weeks I found there is no global 404, you can't use things like window and document, server components are close to useless”
regret · personal · 0.04 yr · YetAnotherNick · 2023-06-25 · source ↗ · wrong label?“I recently tried Nextjs and Remix to explore other stacks... You won't find the dev UX you take for granted in Elixir and Phoenix.”
regret · personal · sergiotapia · 2022-12-20 · source ↗ · wrong label?“the ability to easily use Edge functions now in any NextJs project.”
endorse · production · dalicommerce · 2022-12-17 · source ↗ · wrong label?“we migrated our data-heavy site Classic.com from Next.js to Phoenix + LiveView + Surface.”
regret · production · tlack · 2022-10-07 · source ↗ · wrong label?“We run a Next app on Heroku and we had to disable such component because it was making the app consume in average 500mb of RAM.”
regret · production · mr90210 · 2022-07-10 · source ↗ · wrong label?“Last six months with my last employer I spent immersed in the full Next, React, Prisma ecosystem. I swear that 80% of developers' time was wasted”
regret · production · 0.5 yr · abraxas · 2022-07-02 · source ↗ · wrong label?“The project started as a Next.js SPA and after we needed to add authentication, translations and background jobs things became so crazy and so "custom" that we ditched it”
regret · production · midrus · 2022-03-05 · source ↗ · wrong label?“I run 3 non trivial Next.js apps in prod.”
endorse · production · freedomben · 2021-12-18 · source ↗ · wrong label?“we decided to move to a custom Next.js app in as little time as possible. Big mistake.”
regret · production · scottc · 2021-12-16 · source ↗ · wrong label?“We have a similar stack (React + NextJS + TypeScript + Mobx)... The primary reason we chose NextJS (with SSR) was to be able to write a declarative React component”
endorse · production · drewpc · 2021-09-21 · source ↗ · wrong label?“Overall I think we're down to around 5-10% of the way things were done before, which was -- you guessed it -- hit the DB on every page load _just in case_.”
endorse · production · fbrchps · 2021-09-07 · source ↗ · wrong label?“With Next it has been a much different story. Issues are unblocked routinely and the maintainers seem much more engaged and productive.”
endorse · production · steve_adams_86 · 2021-06-15 · source ↗ · wrong label?“I've also built a few prototypes in Next.js and got near-perfect speed scores without optimizing anything.”
endorse · personal · arcturus17 · 2020-12-23 · source ↗ · wrong label?“from our limited experimentation, has much better ergonomics”
endorse · personal · talolard · 2020-12-16 · source ↗ · wrong label?“After Next announced their support for static site generation and the release of next-serverless, we took the next three weeks to get our site ported over and haven't looked back since.”
endorse · production · himynameistimli · 2020-10-03 · source ↗ · wrong label?“NextJS has been an absolute, undocumented nightmare at our company we've gone back to CRA and 'hand rolled' SSR to retain our sanity.”
regret · production · 1_player · 2020-01-10 · source ↗ · wrong label?“I'm using it on a fairly sizeable project for a client and I'm happy with it so far.”
endorse · production · jypepin · 2019-01-20 · source ↗ · wrong label?“we switched to next.js (with styled-components and apollo-client) and things have been far smoother.”
endorse · production · scottmf · 2017-03-28 · source ↗ · wrong label?“NextJS/Shadcn web app, postgres db, eve agent layer”
neutral · production · atonse · 2026-09-23 · source ↗ · wrong label?“We ported one prototype to Next.js and hosted on Vercel in a couple of days”
neutral · production · jeremyjh · 2026-04-24 · source ↗ · wrong label?“I have been using Next.js for a long time and I have never once interacted with Vercel.”
neutral · production · hmokiguess · 2025-12-12 · source ↗ · wrong label?“We had a pretty bad experience with it on a NextJS app and had to gut it out”
neutral · production · atonse · 2025-04-22 · source ↗ · wrong label?“in my recent experience anyway, we had using Prisma / Nextjs. We switched over”
neutral · production · komali2 · 2025-02-11 · source ↗ · wrong label?“though I've been using Next.js more often recently”
neutral · personal · tan-z-tan · 2024-12-26 · source ↗ · wrong label?“We run Next.js on our own server as we use node-specific APIs in various backend-y places of Next”
neutral · production · theogravity · 2024-11-20 · source ↗ · wrong label?“Worst auth experience: Firebase on NextJS. Never again.”
neutral · personal · throwaway77385 · 2024-10-23 · source ↗ · wrong label?“I was really happy to discover Vite so I don't have to change the way my whole app works with Next.js.”
neutral · personal · Noumenon72 · 2024-10-17 · source ↗ · wrong label?“Here's our experience with Supabase at https://automark.io (Next.js + Supabase).”
neutral · production · jmeyer2k · 2024-04-15 · source ↗ · wrong label?“I've built my own websites running on NextJS, Django, Rails, Jekyll, and Hugo and it was great as a developer”
neutral · personal · abhiyerra · 2024-03-21 · source ↗ · wrong label?“Writing rails api with a nextjs ui, anyone got any suggestions on alternative paths i should take?”
neutral · production · verelo · 2023-12-28 · source ↗ · wrong label?“I've been using Next.js for a couple of years now so I haven't been to React's website in quite some time.”
neutral · production · 2 yr · nathan_tarbert · 2023-12-20 · source ↗ · wrong label?“tend to stick with Next.js if I have a choice.”
neutral · production · nathan_tarbert · 2023-12-11 · source ↗ · wrong label?“This is a short blog post on how we use Next.js redirects to go around all ad-blockers!”
neutral · production · skoshx · 2023-12-07 · source ↗ · wrong label?“When debugging SSR in Next.js, I have a script to spin up mitmproxy and configure Next.js to send requests through it.”
neutral · production · chatmasta · 2023-03-20 · source ↗ · wrong label?“during our spike to test them both out Astro came on top on ease of use.”
neutral · personal · kkarimi · 2023-01-24 · source ↗ · wrong label?“(along with Next, Nuxt, Gatsby, Hugo, and many others)”
neutral · production · 3 yr · naet · 2022-12-10 · source ↗ · wrong label?“the routing section is more intended to explain how we migrated `react-router`-style routing to `next/router`-style routing”
neutral · production · adchurch · 2022-10-24 · source ↗ · wrong label?“We use NextJS as our web framework, so we just write pure web frontend/backend code”
neutral · production · presentation · 2021-12-27 · source ↗ · wrong label?“we switched over to Next recently to take advantage of SSR.”
neutral · production · lattice_epochs · 2020-09-11 · source ↗ · wrong label?“we migrated a webflow site to Next.js/GraphQL/Contentful/Hasura stack.”
neutral · production · zed88 · 2019-08-07 · source ↗ · wrong label?