3 ms·
I've been half-jokingly advocating for "resumable SSR" components that abuse wasm as an isomorphic, serializable coroutine runtime: start rendering a component
by chatmasta 3y ago
I've been half-jokingly advocating for "resumable SSR" components that abuse wasm as an isomorphic, serializable coroutine runtime: start rendering a component inside a wasm VM on the server, while simultaneously serializing and streaming the state of the wasm VM to the client, and then resume rendering on the client.
It's a bit of a meme that takes the idea of "React Server Components" to their logical extreme. And coding a PoC is beyond my capabilities... but I'd love to see someone do it.
- rezonant 3y agoThat's... a really cool idea
- jokethrowaway 3y agoSounds cool but in practice downloading a wasm bundle is bandwidth heavy and rendering to the dom in a browser is different than rendering to a string.
- kamikaz1k 3y agoHave you heard of Qwik framework? Not really you’re suggesting implementation wise, but they have their own idea for resumable rendering.