next-react-server-components

I'm starting to see this demo being used in performance comparisons in a way that implies this is the canonical RSC experience. It would be good to either solve or document (in README) concrete issues with it so that a future reader has an idea of what's correct and what's a known issue. (I've added https://github.com/reactjs/server-components-demo/pull/57 to the original demo in the same spirit.) Update The up-to-date list of problems (likely non-exhaustive) is here: https://github.com/vercel/next-rsc-demo/issues/13#issuecomment-988438962 Streaming "Jank" This demo shows each story "streaming in" individually: https://user-images.githubusercontent.com/810438/145104379-12b00f2d-9eb9-4434-b98b-b48036aa43ad.mov This is a rather janky user experience. I am guessing that this demo does it to make the "streaming" aspect obvious. However, I am observing that people take away that this jankiness is what we mean by "streaming". It seems like a rather unfortunate consequence if people's takeaway becomes that apps built with Server Components have pieces randomly "popping in" — especially because the whole point of the `` won't be in 18.0 and will come later in 18.x. It's not currently implemented on the server. Additional server request I am seeing an extra request to the RSC entry point from the client after the page loads: I wouldn't expect the initial page load to need to make any additional requests. Do we understand why it happens? Is this a bug or a known limitation of the current demo? Thanks I very much appreciate the work on this demo. I'm hoping we can fix and/or document the issues in it so that people are aware what's missing and don't make an impression of the overall RSC architecture or user experience based on an early demo. Thanks!