I don't think I really get the new wave JS frameworks (namely Remix.run and Next.js, but Gatsby might fit there too, if it's still relevant). Either these frameworks are way overcomplicating things, or they're skating to where the puck is going to be, and I'm not there yet.
I wish that these frameworks would build a client bundle and a server bundle locally, and I could decide what to do with them. Like, maybe I could upload them both to some sort of VPS, set up nginx in the right way, and have myself a mostly-static site and a backend type thing, both derived from the same React-ish source code. Or I could upload both to Netlify or Vercel and get all the global distribution and caching that their infrastructure handles. But as it stands, none of these frameworks want you to think too hard about what happens between pushing to your Git remote and when they deploy your stuff, because they're doing a ton of optimization in between in the name of speed.
Justin pointed out that this is a setting that Next.js supports! When I originally tried their Static HTML Export setting, there was some issue with deploying the final output to Netlify, but I'll have to check back in there. If you're okay being on the non-standard path and losing some features, this might be a reasonable choice.
These frameworks also have powerful enough marketing arms (and sparse enough documentation) that I also can't figure out if a single one is meant for me or not. When I run into rough edges, nothing is there to either tell me that I'm doing something wrong, to tell me that they just haven't put enough work into that part of the framework or to tell methat I'm just not the type of website builder that they're trying to capture in their potential market.
I've been spending some time working on a redesign of this site, and I'm happy with the visual language I've put together, but I'm not really excited about building it out in any of the templating languages available to me in Eleventy—I like the idea of building out my UI in React/JSX, and having the framework know what can be server-side-rendered and what it should hydrate on the client. But it seems like once you want that, you have to deal with the server-side mystery meat of the new wave JS frameworks.