I've been checked-out of the SSG world for a couple years and am now evaluating different tools and frameworks for a project at work.<p>I'm intrigued by the direction being taken by Remix, which posits that today's backend options are so improved compared to those of the recent past that they (arguably) have eroded the utility of a static site, period.<p><a href="https://remix.run/blog/remix-vs-next" rel="nofollow">https://remix.run/blog/remix-vs-next</a><p>When it's not crazy difficult or expensive to have a very fast app _and_ database close to your users, you don't have to architect around that deficiency, which is what SSGs are designed to do.
What does next.js offer if server side rendering is of no relevance? It seems to me that ssr adds a lot of complexity and a great number of projects have no need for it at all.
I'm one of the engineers that worked on this - would love to hear any thoughts or feedback anyone has! How does your team deploy your Next.js frontend?
I'm so excited about this . It's a testament to how well-built-up modern frontend tooling is, especially around React. The things that used to take hundreds or even thousands of lines of config can now be done in a few dozen at most with managed libraries. And better!
I mean good for them for improving their user‘s experience. I am just surprised that maintaining your own webpack config seems like such challenge. Enabling chunks to split code to improve loading times or dynamic imports, it‘s not exactly rocket science. Yes DX and all improved as well, but CRA is such a bad choice for production code. It gets you going fast(er), but as soon as you have to tweak it, it seems like devs jump to the "next" framework that already has those tweaks builtin…until they hit the next roadblock. Thus you never learn what actually makes it all work.
The problems described in the "Routing" section are trivially automated. You do not even need a separate data loading library because react-router-dom ships one.<p>The problems described in the "Styles" section would have been solved by migrating to a modern bundler: vite.
What cause the performance improvement?<p>Maybe I missed this detail. I couldn't find anything on why the performance improvement happened when they moved from CRA to Nextjs