Rendering Dilemma: Reacting to State Change
summary
Live demos show a pair of counters: a vanilla React version and a signals version using Solid, with two counters demo proving the difference — React re-renders parents and children until memo prevents parent-triggered re-render while Solid’s signals update text nodes only. The talk names tools and variants: million.js, react forget RFC, useRef, createSignal/createStore/createResource, and argues signals are synchronous, hot-start and multicast while observables are cold and unicast; fragile fine-grain reactivity needs linters and helpers but the Solid approach reduces DOM churn and it works in the demos.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 2:38Why this talk
- 5:07Virtual DOM and React rendering
- 8:14Context and memoization
- 10:46Optimizing renders with memo
- 15:22Avoiding unnecessary work
- 16:48Signals with React
- 18:15Solid.js and signals
- 20:45Signals and Observer pattern
- 22:17Signals vs RxJS
- 24:46Data vs rendering with signals
- 26:30Signals trade-offs in Solid.js
- 28:38Solid.js reactivity helpers
- 32:06No free lunch in reactivity
related talks
17mDissecting Reactivity Signals Vs vDOM
06mEmbracing Reactivity: Signals Unveiled in Modern Web Frameworks
28mSolid for React Developers
21mUnderstanding Rendering Patterns
28mSignals: What, How, and Why!
29mSolidJS - Reactive JSX
31mUnderstanding Rendering Patterns
18mIntro to Solid.js for React Developers (or anyone else)