Nextjs

FIRST-HAND READS

What people reported, in their own words. Every line links to where it was said.

• “I have never had issues running Nextjs in regular containers, it is just a good open source solution”

  POSITIVE · reliability · Hacker News · 2026-07-07

• “They were a mess. NextJS, React, about 4 micro services for a site that had 50 users per WEEK.”

  NEGATIVE · reliability · Hacker News · 2026-06-05

• “if I could go back I would probably reconsider the "everything in typescript" and "lets use nextjs, it's what everybody uses" and reach for something more performant”

  NEGATIVE · performance · Hacker News · 2026-05-12

• “nextjs works well with its nested routing and layout-to-hold-context magic. it's quite nifty”

  MIXED · features · Hacker News · 2026-05-09

• “it was a nextjs SPA frontend with a separate API backend, the user facing urls didn't match the backend endpoints”

  NEGATIVE · features · Hacker News · 2026-05-09

• “NextJS' dev server takes around 3-4 GB memory after a few page click”

  NEGATIVE · performance · Hacker News · 2026-04-14

• “any new site I build is on NextJS since coding agents make it a breeze”

  POSITIVE · ease of use · Hacker News · 2026-04-10

• “not sure why NextJS builds take so much, we are using stable and functional pages router in DollarDeploy and it is still takes too much time to build”

  NEGATIVE · performance · Hacker News · 2026-04-08

• “most frustrating thing about working with NextJS. There seems to be no way to improve the speed of building the app.”

  NEGATIVE · performance · Hacker News · 2026-04-08

• “nextjs is really fantastic with LLM usage because there's so much body of work to source from”

  MIXED · ease of use · Hacker News · 2026-03-25

• “they decided to go with nextjs and required 3 people fulltime to maintain this, including all the usual churn and burn of updating dependencies and changing the "router" and stuff. Porting a menu from one instance of the frontend to another frontend took 3 weeks. Fixing a menu display bug after I reported it took 2 or 3 months.”

  NEGATIVE · ease of use · Hacker News · 2026-03-22

• “migrated away from NextJS for similar reasons of being too special case in the ecosystem. Next in particular is designed for the way Vercel runs applications and comes with extra pain if you don't run on edge.”

  NEGATIVE · ease of use · Hacker News · 2026-03-21

• “they keep changing random shit around for no reason, we've had to waste time on multiple refactors already for major nextjs version bumps once the older ones are no longer supported”

  NEGATIVE · reliability · Hacker News · 2026-02-24

• “I let it run nextjs with an ORM, and it almost always creates very well defined api routes, classes & data models”

  POSITIVE · features · Hacker News · 2026-02-07

• “I didn't think it was possible for me to dislike nextjs any more”

  NEGATIVE · Hacker News · 2025-12-18

• “I am building an application using nextjs as the only backend and have not run into any issue and it is currently more than 25,000 lines of code. It is highly likely you will never have to implement an independent backend even at a very big scale.”

  POSITIVE · performance · Reddit · 2025-05-17

• “I'd say the entire past few major versions of NextJS are less important than having working middleware. This affects stuff as basic as auth flows and observability.”

  NEGATIVE · features · Reddit · 2025-05-16

• “all those other normal NextJS features works too - SSR, static prerendering, SEO optim, auth, image optimisation, etc...”

  POSITIVE · features · Reddit · 2025-03-02

• “NextJS rolled back years of tooling improvements, it's much slower than Vite”

  NEGATIVE · performance · Hacker News · 2025-02-09