It's Time To Talk About Signals
summary
Explains what signals are, builds a working demo of a reactive system in 30 lines of JavaScript, and shows how signals track subscribers, compute derived values, and run effects. Demonstrates real problems—recalculation order, intermediate glitches, and the need for batching and topological dependency ordering—and shows optimizations like dirty-tracking and on-read evaluation. Notes ecosystem status: frameworks (Vue, Svelte, Solid, Angular) adopt signals, React resists, and there is a TC39 stage 1 proposal with polyfills for experimentation.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:14What are signals
- 3:40State in front-end
- 5:25SSR to client DOM
- 8:34Frameworks and observables
- 11:23Frameworks adopting signals
- 16:56Why React avoids signals
- 23:25React’s signal experiments
- 25:34How signals work
- 31:02Developer benefits of signals
- 34:42Basic signal system
- 39:00Signal implementation challenges
- 41:04Optimizations in signals
- 44:16TC39 signals proposal
- 47:50Q&A
related talks
27mA Deep Dive into Fine-Grained Reactivity and the future of Signals
48mJS Signals
46mSignals from Outer Space
06mEmbracing Reactivity: Signals Unveiled in Modern Web Frameworks
30mAre Signals worth the hype?
37mReactivity and Signals: Demystifying Frontend Magic
29mRevolutionary Signals
17mStandardizing "Signals" in TC39