Revolutionary Signals
summary
Explains signals as three concrete primitives — signal, memo, effect — and shows a <50-line runtime implementation using a global stack that tracks subscriptions. Demonstrates a working DOM counter that updates one text node without a virtual DOM, a movies app that ships ~13 KB taste-movies demo of interactivity by sending only dynamic bits, and a resumability approach that serializes reactive state to avoid hydration. Shows DevTools tracing of dependency flows and claims glitch‑free, schedulable updates and lower memory use.
AI-written summary · about
chapters (19)
- 0:00Introduction to signals
- 1:06Signals in JavaScript history
- 2:50What are signals
- 4:37Signals primitives explained
- 7:25How signals work runtime
- 10:14Benefits of reactivity
- 11:41Building a counter demo
- 13:46From manual to JSX
- 16:54Signals without virtual DOM
- 17:59Signals in component libraries
- 19:03Component boundaries and signals
- 19:46Optimizing static and dynamic
- 20:50Scaling interactivity
- 21:52Taste movies app demo
- 23:19Eliminating hydration
- 24:21Dev tools for signal tracing
- 25:24Signals vs legacy frameworks
- 26:06Predictable execution guarantees
- 27:08Takeaways and future
related talks
52mIt's Time To Talk About Signals
17mDissecting Reactivity Signals Vs vDOM
34mBeyond Signals
42mReactivity and signals demystifying frontend magic
06mEmbracing Reactivity: Signals Unveiled in Modern Web Frameworks
30mAre Signals worth the hype?
27mA Deep Dive into Fine-Grained Reactivity and the future of Signals
31mThe World Beyond Components