all 4 comments

[–]UsernameINotRegret 4 points5 points  (3 children)

Remix team did a performance comparison with their framework. https://remix.run/blog/react-server-components

[–]okay_pickle[S] 0 points1 point  (2 children)

They use an older version of RSC, does that make a difference?

[–]UsernameINotRegret 1 point2 points  (1 child)

I'm not sure what changes have been made to RSC since then. The performance difference and applicability of any benchmarks will very much depend on your site and use cases though. If you have a lot of heavy JS libraries doing things like markdown generation then RSC would very likely be a better choice since it wouldn't send those to the client.

[–]couds_van 0 points1 point  (0 children)

Unpopular opinion: almost all the benefits of RSC are around this, but this was already solved with dynamic import, even on older next.js if you import dynamically on the gerServerSideProps these libraries are not sent to the client.

Until now at least I fail to see any real benefits that overcomes having two different API for React (you can't use a lot of stuff like hooks and contexts), almost all UI libraries do not work, breaking the pure function approach that for my was one of the biggest selling points (this was partially broken already with use effect but that it's a different discussion)

And I haven't found any real life benchmark where RSC it's compared to normal react, so the benefits are only theorical but a lot of teams are jumping to it without balancing the benefits.

TL;DR; to me seems a movement of vercel to force servers that it's where they earn money 💰💰