3 ms·
I like React a lot... but tbf, I never really quite agreed with the RSC push in general. I think most web-based apps are fine with client-render against an API
by tracker1 1y ago
I like React a lot... but tbf, I never really quite agreed with the RSC push in general. I think most web-based apps are fine with client-render against an API/GraphQL/WebSocket backend. RSC is just a few steps too far in both Pure-Fucking-Magic (PFM) and rigidity in approach.
If there was a component library as complete as MUI for Yew/Dioxus/Leptos I'd have likely already switched to Rust/WASM.
- kaoD 1y agoPersonally I really wanted RSC because I have a DIY SSG based on React. It's dead simple but only supports static components. Something like RSC would allow me to automatically cook a bundle with only the interactive parts (think e.g. a custom dropdown or whatever) while still remaining fully static. Now I'm not so sure given how they're developing... [0] https://github.com/alvaro-cuesta/alvaro.cuesta.dev/tree/master/xenon-ssg https://github.com/alvaro-cuesta/alvaro.cuesta.dev/tree/mast...
- BoorishBears 1y agoRSC should never have made client support opt-in. During RFC it was identified as a problem, but Shopify and Vercel pushed for an intentional breakage "for the greater good" in driving adoption. (conveniently ignoring that they're likely two of the only platforms that will ever want to take on the complexity of a non-toy RSC deployments)