this post was submitted on 09 Jul 2023
10 points (100.0% liked)
React
923 readers
1 users here now
A community for discussing anything related to the React UI framework and it's ecosystem.
Wormhole
Icon base by Skoll under CC BY 3.0 with modifications to add a gradient
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I have been enjoying it! I think the RSC data fetching pattern is really nice, and it simplifies the logic of the app. It's also really nice to have the same pattern for non blocking fetching (use suspense to show loading states), blocking fetching with ssr (no suspense), ssg (cache the fetch indefinitely/fetch on build), or isr (cache with revalidation time), and to be able to granually config the behaviors on the individual fetch level.
There still some rough parts, most notably imo is the caching/revalidating side of things. Maybe I didn't do it right, but I was struggling hard ro invalidate caches to show updated data after mutation 🥲 I currently just set all the fetches to no cache right now, and for now it is fine (i dont have so much traffic on that project that it causes an issue, just me and some of my friends testing things rn). Imo caching should be an opt in thing for optimization rather than a default, but I think thats more of the Next's specific implementation rather than rsc in general.