server-components-notes-demo VS next-react-server-components

This is the last I heard about it https://github.com/vercel/next-server-components

There is a number of public, easy-to-understand projects you can check out after you've digested all the new patterns from the docs (and maybe that tutorial): https://github.com/shadcn/next-contentlayer https://github.com/vercel/next-react-server-components

In the official Next.js demo both approaches are mixed together. But aren't these different approaches?

In the Next.js demo, SSR Streaming and React Server Components are presented together within one demo. Aren't the two approaches two different technologies that can be used independently?

For comparison this[1] is Next.js implementation that uses React Server Components (RSC). I feel folks at Remix missed on React Server Components and now it will be a lot of work to make it work in Remix. Hopefully I'm wrong.

If you don't know, RSC allows the HTML from server to start streaming as React is rendering the components in the backend. It allows fine grain control to what part of page renders first and which parts can be rendered later as HTML and data is streaming from the server. Before this, all of React server frameworks would render the entire page, shove "hydration data" in it which is mostly repeated data that is used to render the page and also include that HTML in the form of complied JSX in the page in the page scripts. Obviously that would make React SSR very bulky and unscalable. That's why RSC can solve so many React performance problems

[1] https://github.com/vercel/next-react-server-components