React Server Components
@dan_abramov: @delba_oliveira @pomber @asidorenko_ this is a really bad graphic but it’s kind of more like this in my mind https://pbs.twimg.com/media/FqidRzFWAAk_q4w.jpg
@dan_abramov: i wonder if something like this might be a helpful mental model for how and when RSC runs https://pbs.twimg.com/media/FqueyH_WcAILs7c.jpg
10’s: Figuring out the client
20’s: Composing server and client as one paradigm
React is doing this with Server Components, but it is not going to be alone. This is a broader shift defining the next generation of frameworks.
"refresh Server content in place without losing Client state"
"nested routing let you fetch data in parallel"
"you provide local visual feedback for a refetch"
"you build a full-stack app without exposing any REST/GraphQL APIs to the client"
@the_spyke: @dan_abramov 30’s: Web break free from HTML/CSS. A native full stack app renders itself via WASM/WebGPU however it likes with smooth frame rates and low memory consumption. @samselikoff: I think it'd be pretty sweet if we could have Server Components and Client Components in the same file 🤔 https://pbs.twimg.com/media/FodvB-uWICMxQxx.jpg