News for hackers. Stuff that matters.
Re:Remix vs. Next.js by cockatiel_day on Wednesday January 19, 2022 @10:16AM (#29994621)
Remix's approach to fetching is unique and compelling for Rest APIs.

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.

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.

Re:Remix vs. Next.js by omgsean on Friday January 21, 2022 @12:39PM (#30026972)
GraphQL comes with its own set of headaches though, especially if you're the person responsible for implementing the server.
Re:Remix vs. Next.js by pier25 on Tuesday January 25, 2022 @11:06AM (#30073421)
Exactly.

Plus, if you're using something like Remix, you don't need an API layer anymore. The data goes from the query straight into the view.