Haven't heard of Remix, will give it a try. One thing that bugs me with Next.js is the missing data mutations part that Remix claims to address. When I setup my next.js project and was fetching data via getServerSideProps I was impressed. Until I realised there is <i>zero</i> support for mutating data. As soon as I need a single POST/PUT request, next.js support ends and you are back to writing your own fetch() code. It somewhat felt as if developers ended their day there, as you would definitely expect <i>something</i> that allows you to send data from the client to the server.
Remix's approach to fetching is unique and compelling for Rest APIs.<p>However, if you're working with a GraphQL API, you can eliminate all these much-mentioned fetch waterfall issues by using Relay as a client... Relay inspects the data needs of all your page's components and compiles them to a single page query. Relay also has a number of nice developer interfaces for common/annoying problems like pagination that I don't think are possible w/ Remix's approach.<p>This article is informative, but I think it misleadingly implies that you can't avoid waterfall fetches in Next (or that it only might be possible someday w/ React Server Components)... you can.
I’ve been pretty deep into next js for a while. I’m excited to give Remix a try.<p>Very big fan of fly.io as well, they’re smart folks and I run every service I can on them.
I started to use Remix and I love it, the nested routes / layouts is the most powerful feature for me. Also, the API is easier and cleaner than Next and the hooks to consume the data is a nice approach as well.
Glad to see someone not focused on frontend.<p>Frontends are incredibly bloated already and next.js embedding react in any page is a killer for static websites.