Understanding Rendering Patterns
summary
Compares the VDOM batching model with fine‑grained signals and shows live demos: a React counter that re-renders twice in dev, fixed by React memo and the upcoming React Forget RFC, versus a SolidJS counter where updates touch only the changed value. Lists concrete primitives used: For/Index for list stability, createStore and createResource for tracked objects and async, and the rule “do not destructure props.” Claims signals reduce unnecessary renders but require careful helpers and different ergonomics.
AI-written summary · about
chapters (16)
- 0:00Introduction and welcome
- 1:04Rendering patterns overview
- 3:57Virtual DOM explained
- 7:33Context and excessive renders
- 8:56React Forget and memoization
- 10:02Counter demo with React
- 13:55Challenging the virtual DOM
- 15:42Fine-grained reactivity with signals
- 16:26Solid JS demo
- 18:13Observer pattern deep dive
- 21:04Signals vs React State
- 22:09Signals trade-offs and pitfalls
- 23:12Solid JS helpers and reactivity
- 26:44Key takeaways and no silver bullet
- 27:50Signals in other frameworks
- 29:56Summary and closing
