Beyond Signals
summary
Claims that signals plus a reactive data graph remove the VDOM and let updates hit only changed fields, demonstrated by nested async fetches that each take 2s but render in parallel and by an 80-line to‑do backed by a 400ms mock DB where optimistic stores show updates immediately while background sync saves them. Shows proxy-based stores that make deep properties independent, an error boundary that retries by walking the reactive graph, and a new primitive projections to fork granular, derived reactivity.
AI-written summary · about
chapters (17)
- 0:00Signals introduction and impact
- 2:33Signals performance myths
- 5:44Fine-grain rendering benefits
- 6:04Mutability in reactivity
- 8:55Introducing projections
- 10:00Derived signals and side effects
- 11:02Async handling in UI frameworks
- 13:31Demo: Parallel async data fetching
- 15:55Push vs pull reactivity
- 16:21Demo: Async error handling
- 19:14Consistency models for async updates
- 20:57Demo: Optimistic UI updates
- 25:35Future of signals and graphs
- 26:18Q&A: Proxy vs non-proxy signals
- 28:45Q&A: Async components vs signals
- 31:14Q&A: Sequential vs parallel async
- 32:38Q&A: Async data fetching flexibility
