"Because the RSC protocol is an implementation detail of React, it is not explicitly documented outside the source code."
it's wild
danabramov•1mo ago
What?
brazukadev•1mo ago
It is not a protocol if it is a React's internal implementation detail. This is quite obvious, no?
And quite "weird" decision, as some of people implementing this detail also work for Vercel, the one benefiting the most from the undocumented apis.
danabramov•1mo ago
I mean "protocol" in the sense of "wire protocol" or "serialization format". Is that clearer?
>And quite "weird" decision, as some of people implementing this detail also work for Vercel, the one benefiting the most from the undocumented apis.
There is no dependency on the wire protocol in any of Vercel's code. (It wouldn't work since it breaks between versions and would be very fragile to do. That's the whole point of doing it as an implementation detail of React.)
The protocol (de)serializer is in the React repo and is 100% open source. It was designed by the person who led the React team at Meta, and it was created before Vercel contributed any code to React.
b6dybuyv•1mo ago
it's wild
danabramov•1mo ago
brazukadev•1mo ago
And quite "weird" decision, as some of people implementing this detail also work for Vercel, the one benefiting the most from the undocumented apis.
danabramov•1mo ago
>And quite "weird" decision, as some of people implementing this detail also work for Vercel, the one benefiting the most from the undocumented apis.
There is no dependency on the wire protocol in any of Vercel's code. (It wouldn't work since it breaks between versions and would be very fragile to do. That's the whole point of doing it as an implementation detail of React.)
The protocol (de)serializer is in the React repo and is 100% open source. It was designed by the person who led the React team at Meta, and it was created before Vercel contributed any code to React.