SolidJS: Why all the Suspense?
summary
SolidJS treats Suspense as a concrete mechanism for async consistency not just spinners, using resources (async signals) to cache promise factories, nested suspense boundaries to control fallbacks, and startTransition to isolate updates so UI can “stay in the past.” Demos show parallel fetches, SSR streaming with FirstStream True, a 15‑line optimistic mutation layer, and an experimental scheduler that smooths a 500‑item render. Each demo runs and demonstrates practical tradeoffs and where tearing, waterfalls, or optimism are solved.
AI-written summary · about
chapters (16)
- 0:00Intro
- 3:44Facebook Messenger
- 6:12Async tearing
- 8:40Three options
- 9:30Definition
- 10:14Suspense is not okay
- 11:03Suspense based on reads
- 13:02Live coding
- 18:13Promises
- 19:25Handling Errors
- 25:45Stay in the Past
- 26:19Transitions
- 29:40Global
- 32:10Mutation
- 37:40Radar
- 41:25Conclusion
related talks
26mReact Suspense
22mRoad to a better UX with Suspense and Concurrent UI
09mRoad to a Better UX with Suspense and Concurrent UI
20mThe suspense quest Inside React's Magic
43mAsync
18mExploring React 18's Streaming Capabilities with Suspense for SSR
29mSolidJS - Reactive JSX
39mReact … wait for it … Suspense