Gaurav thakur
255 posts

Gaurav thakur
@gauravcodes
Building https://t.co/6KMzkJCraa | https://t.co/TiWsKQkLIp | https://t.co/KcadcgP7Nl | Frontend @zeptonow | Web Enthusiast






Simple interaction: one select changes the options of a second with a remote data source How would you build it? How do you deal with race conditions?




I don't really understand the RSC hate. You're getting angry at a tool. If you don't need it, just don't use it. RSC is just another option for serializing and hydrating JSX and interactive components. I get that the NextJS App Router approach to using the RSC functionality might not have worked in your use case. And that's totally valid take. But it's not a reason to hate the underlying tool. Not all tools work on all jobs. There are lots of ways to use the underlying RSC functionality, and we are just starting to see those come out. For example; a SPA application could make a server call and get back Flight data (the format of RSCs) and hydrate that on the fly, loading in the interactive code only when necessary. This would reduce bundle size dramatically and speed up the initial load of the app. And that's just one of many possible options to leverage RSC. Has it taken too long to get to RSC options outside of the App Router model? Perhaps. But RSC is a major addition to the underlying React toolkit, so of course it's going to take a while for framework authors to understand it and to see if it fits their model, or not. But I don't think it's helpful to just hate on RSCs entirely because you don't dig the NextJS App Router. If the App Router isn't matching your use cases don't use it. There are new models of RSC interaction on the way, from Waku and @tan_stack Start. And those might provide you options based on RSCs that do work for you. Or not. Either way, RSC support existing in the framework does not hurt your SPA app.

We are trying to render a paginated page (it is basically a list of RSC with some nested client components for some client logic) using infinite scroll, where the next page will be fetched with the help of an Intersection Observer. (1/n)













