- Separation of SSR vs RSC rendering environments is both unnecessary and a pain point for existing application migration to the new paradigms.
- "Client Component can't import Server Component" seems to be an artificial limitation of the mental model of separate SSR vs RSC env and the lack of built in support for inlining RSC streams into the HTML document
- Removal of "client only hooks" is also an artificial limitation brought on by trying to make SSR and RSC independent concepts. Zero reason to remove hooks that work in SSR today to support RSC.
- Inlining of RSC JSON representation should not be needed and the intermediate tree should be able to be revived from the SSR'd DOM, not an inlined RSC format.
Created
February 28, 2023 18:44
-
-
Save jacob-ebey/1f4f127bd5ca2dcf47c5e74f9f35f6b6 to your computer and use it in GitHub Desktop.
RSC Exploration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment