by pspeter3 on 1/18/22, 6:55 PM with 16 comments
by littlecranky67 on 1/19/22, 10:48 AM
by cockatiel_day on 1/19/22, 3:16 PM
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.
by austinpena on 1/18/22, 10:38 PM
Very big fan of fly.io as well, they’re smart folks and I run every service I can on them.
by nsonha on 1/19/22, 12:44 AM
by jmtucu on 1/19/22, 10:52 AM
by pictur on 1/19/22, 4:40 AM
by jokethrowaway on 1/19/22, 7:11 AM
Frontends are incredibly bloated already and next.js embedding react in any page is a killer for static websites.