Reason I like RSC is because it removes the boundary between server and client. You get server components that run sql and pass results into client components as props. And you get client components importing server functions that mutate your db. server/client gap is reduced to an import statement - ThreadSky

About ThreadSky

ryantoron.to • 211 days ago

Reason I like RSC is because it removes the boundary between server and client. You get server components that run sql and pass results into client components as props. And you get client components importing server functions that mutate your db. server/client gap is reduced to an import statement

Comments

ryantoron.to•211 days ago

To me RSC is a collection of features and ideas that shrink the gap between server and client. I think you need all the APIs in RSC to make that happen, and focusing on only a select few loses the forest through the trees. So not about smaller bundles, html, or serialization (for me at least)

devagr.bsky.social•210 days ago

You can shrink this gap without RSCs as well

ryantoron.to•210 days ago

Ya, true. I love seeing all the frameworks experiment with their own versions of this. I still think it's worth having something like RSC built into React though. We're all writing backends to support client React apps and now we have a first class way to do it. That seems like a good thing?

devagr.bsky.social•210 days ago

Not when this first class way comes with serious limitations

ryantoron.to•210 days ago

What are the biggest limitations for you? What kinda stuff have you run into?

devagr.bsky.social•210 days ago

dx wise it's a massive architectural shift from client-first to server-first, the composition rules are awkward, you can't simply fetch data anywhere without ensuring the entire tree upwards is server components, and you still have to do manual hoisting to avoid waterfalls

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply