How you can Server-Render without Rendering on the Server
summary
Claims a practical path to server‑driven UI that avoids heavy client rebuilds by sending JSX‑like component definitions and actions over websockets, implemented in Node instead of the planned C++ GPU pipeline and driving real hardware: the Uprising app controls 24,000 individually addressable LEDs at Burning Man, prototypes run in production, and edits hot‑reload to devices. The project is released as rise tools with a component kit and a public app Rise playground that demonstrates live server‑defined screens and acceptable performance.
AI-written summary · about
chapters (14)
- 0:00Welcome
- 1:13Breaking technical limits
- 4:21Live demo: server-driven rendering
- 5:48Uprising project story
- 7:17C++ to JavaScript journey
- 8:44What is server-driven rendering
- 10:07Rise Tools for React Native
- 16:52Uprising’s server models
- 17:14Setting up server-driven rendering
- 20:22Simplifying setup
- 21:46Rise Playground
- 22:27Live audience demo
- 32:46Summary
- 33:51Q&A
related talks
34mServer Driven UIs: the future of cross-platform rendering
54mReact Server Components: A New Way to Build Fast and Interactive Web Apps
45mReact Server Components: A New Way to Build Fast and Interactive Web Apps
40mServer-Side Rendering 2.0? React Server Components
04mA few things to know about SSR
50mReact Server Components: A New Way to Build Fast and Interactive Web Apps
10mUniversal Apps: Architecture for the Modern Web
28mServer-Side Apps, Not Server-Side Rendering: A Real Alternative to React
