When Next.js still makes sense: For large existing React codebases, migration costs may outweigh performance benefits. If you’re stuck with React and can’t migrate, consider TanStack Start over Next.js for a 33-35% bundle reduction without App Router complexity. For greenfield projects, though, there’s no legacy to maintain, no migration costs to weigh. Choosing to build on a foundation that costs users 2x to 3x more JavaScript on every visit means voluntarily accepting worse performance when better options cost nothing extra. “We only know React” isn’t a technical constraint, it’s a learning investment decision. And “organizational politics” is real, but it’s not a technical justification. It’s an admission that better options exist but can’t be chosen.
This is painful to read after my team chose Next.js for a brand new project we started last year. 🤦♂️ — via Adactio