3 ms·
I used to really like NextJS. For "webapps" I would reach for the "vite + react-ts" starter and for "websites" I would always reach for NextJS. But over time it
by _fat_santa 2y ago
I used to really like NextJS. For "webapps" I would reach for the "vite + react-ts" starter and for "websites" I would always reach for NextJS. But over time it went from "this is a great framework" to constantly going "nobody asked for this, why is this like this".
It went from a solid react framework for generating websites to one that clearly had use cases in mind and was always pushing you in a particular direction. Whether that would be with Next Image and the inability to statically optimize images at build time to an obsession with react server components.
And with Next Image for example, there was a clear motive to kneecap it and make it so it only really worked inside Vercel (until OpenNext came along). Gatsby could optimize images at build time and there's even an excellent plugin for NextJS that does just that. The devs had almple time to implement this feature however even today it's not available.
I've since switched all my "website" development to Astro and haven't been happier.