Next.js

“Nextjs static export has features such as dynamic chunking, eager-loading of chunks when you hover over a link, routing etc.”

“Nextjs can get you 100 if you use it properly. Like anything it's just a tool that can increase complexity”

“It also made image optimization almost effortless, greatly improving load times for my websites.”

“They have extremely good engineers, but product/feature management can really benefit from some self-reflection”

“It's yet another backend framework, added that it only runs on vercel infrastructure.”

“R3F (ReactThreeFiber), Drei, and NextJS (with OpenNext) save time on generated interactive 3d visuals.”

“reasoning about the behavior and what actually happens in the framework when something doesn't work is increasingly difficult”

“Next.js and TanStack Start don't send any JavaScript to the client if you decide to server-render everything.”

“Leaning into the opinionation it provides/encourages keeps my team from bickering too much about how to structure things.”

“The frustation is pretty much there under Vercel's stewardship, especially when React comes in the shape of Next.js.”

“the complexity tax of a full framework is hard to justify once you measure what you are actually paying in build time”

“They are downloading and executing megabytes of JS while in-page interactions tends to be limited to few basic stuff.”

“Next.js gives us SSR plus built-in routing for 4 languages, ISR for cache invalidation on ~900K pages”

“Next.js really shines, especially with file based routing and ISR making things much easier to manage.”

“Next in particular is designed for the way Vercel runs applications and comes with extra pain if you don't run on edge.”

“Switching from Next's pages router to app router (RSCs by default) is a major shift in architecture”

“We shipped file system caching in 16.1 that greatly improves the initial route loads.”

“This is amazing. At Wasmer we are a bit concerned of Next.js and this replacement might come in handy!”

“Vercel may be bad, but they have been a net positive to the web landscape, so many projects are alive because of them”

“they keep changing random shit around for no reason, we've had to waste time on multiple refactors already for major nextjs version bumps”

“Next is very complex, largely because it has incrementally grown and kept somewhat backwards compatible.”

“With sveltekit(and maybe nextjs aswell) you are only serving the necessary files to the client”

“they did the heavy work of building things that need to already exist when building an application”

“a lot is accidental (backwards compatibility, enterprise features most people don't use, etc.)”

“especially typescript/nextJS projects, and properly documenting all those pieces you mentioned, it goes a long way”

“they made it more server-heavy and changed the paradigm to one where a single page is built up using multiple queries”

“that stack happens to also solve for a lot of problems totally unexperienced people will struggle with”

“they are already pushing Edge Delivery Services which is based in NextJS although it's a different approach”

“they pile new shiny bit on top of new shiny bit without caring about the regular user experience”

“The nextjs tutorial is a remarkable s-tier educational content; it helped me kickstart my journey into full-stack dev”

“other frameworks (thinking mostly of Next+Vercel and Laravel here) are merging their frameworks with hosting”

“Introduction of a complex frontend framework like next seems like it would lead to more headaches than it's worth.”

“One of the reasons Next.js is attractive to me, is exactly they have rediscovered why so many of us have stayed with SSR.”

“it's just good enough with all the backend stuff within the same Next.js process as the front-end”

“Most people assume you can just throw a Nextjs project into a docker container and don't realize that there are many features that don't just work "out of the box"”

“it feels like the first few, early, iterations of Next were great, and then it all started progressively turning into slop from a design perspective”

“it reminds me of the Meta monorepos, where everything related to a certain domain is kept in the same directory”

“Nextjs ups the complexity orders of magnitude, I couldn't even figure out how to set any breakpoints on the RSC code within next.”

“If any of those frameworks at any point did half the things React + Next-like frameworks accomplished”

“Learning and using it was (and is, because now I have to maintain the project) painful, confusing, and full of footguns”