Dissecting Reactivity Signals Vs vDOM
summary
Shows that vDOM forces whole-tree rerenders while Signals track dependencies and update only changed DOM nodes. Live counter demos show React rerenders both counters, memoization prevents some renders but still rerenders when a memoized value is accessed, and a Solid-style create signal implementation updates only the changed text node. Notes tradeoffs: need getters, avoid destructuring props, use helpers like createEffect and stores for objects. Mentions adoption across frameworks and the react forget compiler RFC as a partial middle ground.
AI-written summary · about
chapters (8)
- 0:00Introduction and speaker intro
- 1:44Why discuss reactivity frameworks
- 3:51Virtual DOM rendering model
- 6:38React memoization demo
- 10:13Signals vs virtual DOM
- 12:23Tradeoffs of using signals
- 14:50Signals adoption across frameworks
- 16:57Summary and closing
related talks
34mRendering Dilemma: Reacting to State Change
21mUnderstanding Rendering Patterns
31mUnderstanding Rendering Patterns
06mEmbracing Reactivity: Signals Unveiled in Modern Web Frameworks
29mSolidJS for React Developers
19mSolidJS: Reactivity Unchained
29mSolidJS - Reactive JSX
28mSignals: What, How, and Why!