|
|
|
|
|
by boringuser2
1106 days ago
|
|
I've never seen the use-case. If you're building trivial brochure pages that need SSR for adsense, you shouldnt be using react at all. If you're building complex apps, it doesn't really make much sense to put the burden of rendering on your server. |
|
The RSC part is mostly the streaming of the JSX result, but this only solves the issue that the market wants to work in a MPA way with the routing benefits of a SPA.
Again, nothing new, Turbolinks existed and replaced sections of your HTML with XHR, but you had to slice it up yourself and manage interactions again if the section you changed required JS. RSC takes away the latter part and you're only required to define the boundaries. That's the reason why RSC has it's place, you're able to mix and match it within the same codebase instead of maintaining one codebase for your marketing pages and one codebase for your application (and one for your docs)