Ask HN: The whole NextJS situation is overwhelming NextJS came to save us all, until it became a mess. The front-end framework drama has been going on for at least a decade. Theoretically, could we even have some sane resolution with clear choices within the next 5 years? What can it look like? |
But in my post I was referring to the overall state of the front-end tools right now and the frustration that comes with it. From one side it's the best time to build things and see how far we've come. On the other hand it can feel like the unnecessary complexity of our tools only increases rather than making things simpler, I was interested to hear some ideas of where we might end up with all this and how soon
Unfortunately, options for SSR in React are all pretty limiting compared to other languages' frameworks, unless you go the full DIY route which isn't usually feasible.
Of course, if you don't need SSR there's no reason to chain yourself to Next and Vercel's whims. Starting a React project from scratch is a lot less painful now with Vite (there was a time when just setting up Webpack & stuff took half a work day).
This is just my personal experience, however. I know a lot of people live and die by Next.js.
It won't. You actually remove complexity by removing unnecessary dependencies.
You can organize your code the same way you would with React: components, state management, reactivity. It is all there within JS+HTML+CSS without 100kbytes of minified JS.