4 ms·

The wire protocol isn't relevant -- it's an implementation detail of React, and both the client and the server for it are open source and in the React repositor

The wire protocol isn't relevant -- it's an implementation detail of React, and both the client and the server for it are open source and in the React repository. Next uses those. So will Remix, Redwood, and other RSC frameworks. If you're curious: https://github.com/facebook/react/blob/main/packages/react-client/ https://github.com/facebook/react/blob/main/packages/react-c... https://github.com/facebook/react/tree/main/packages/react-server https://github.com/facebook/react/tree/main/packages/react-s...

halfmatthalfcat 3y ago
Dan, you can't deny that most (if not all) the comms from both the React team and Vercel make it obvious that Vercel is not only first-moving on RSC but working intimately with the React team to both vet the implementation and I'm sure offer (opinionated) advice on tweaks/direction. Also, links to packages with 5 line READMEs and no comments/documentation in the code might as well be called blackboxed. Yes, its open source but that's pretty much it. John or Jane Doe will have to deconstruct and/or assume the team's intention by combing through your links, https://github.com/reactwg/server-components/discussions/5 https://github.com/reactwg/server-components/discussions/5 and the (light) documentation from Vercel on how all this stuff really works. All I'm asking for is clarity and the ability to potentially create my own implementation rather than watch the "big guys" (read: frameworks) get the advantage by having access to information we don't have.