That makes sense. Too bad it was developed in partnership with Vercel. Deep composability seems to serve their needs—it's not a solution the ecosystem was asking for, at least from my perspective.
You're misinformed. However, you speak with enough conviction that it seems pointless to try to convince you of something else. If you're curious about what it actually is, and the actual historical road towards it, you're welcome to read my blog — for example, https://overreacted.io/jsx-over-the-wire/ is a longread on that topic.
Hey, I appreciate your writing and the logical development from A to B to RSC. I just don’t think that 95% of react applications care about this use case, or want to introduce the complexity necessary to support it. But history will tell, I could certainly be wrong.
As for the origin story, didn’t Next run an experimental release of RSC way before it was GA in react 19? I don’t want to take anything away from your contributions to it, and if you can tell me that react 19 was not at all shaped by Vercel I’ll accept that. But it goes against the general perception that RSC is heavily supported by Vercel, to feed into their hosting business.