I'm a @remix_run fan
I'm a @remix_run fan. But, there are valid reasons to prefer @nextjs static builds for some sites:
1. Static files are simple
2. Static files are cheap & easy to host
3. Static files can be hosted *anywhere*
4. Static files are fast on *every* request, regardless of cache status
I know the @remix_run team argues that server-side rendering with state-while-revalidate headers accomplishes the same UX. I agree that's generally true, but as with any technical decision, there are tradeoffs.
Also, I agree with the @remix_run team that most pages aren't truly static, so in many/most cases you'll want to server-render anyway. But for pages that are truly static (blog/docs/etc), I can understand wanting to do static generation for the reasons I mentioned above.