JS Signals
summary
Signals are a reactive state primitive that frameworks like Angular, Solid, Vue and Svelte adopt and a stage one TC39 proposal exists to add them to ECMAScript. Claim: signals improve both developer experience and runtime performance via autotracking and a push‑then‑pull invalidation model. A live-coded JS implementation shows the concept in ~42 lines (signal, computed, effect) but lacks push/pull laziness, error handling and GC improvements the language‑level proposal aims to address.
AI-written summary · about
chapters (7)
- 0:00Introduction to JS Signals
- 2:50What are JavaScript signals
- 16:00Reactive state primitive explained
- 22:22Signals vs stores and observables
- 34:34Why signals are poorly named
- 36:19Live signal implementation demo
- 47:05Current state of TC39 signals proposal
related talks
31mSignals in JavaScript
52mIt's Time To Talk About Signals
46mSignals from Outer Space
17mStandardizing "Signals" in TC39
30mAre Signals worth the hype?
27mA Deep Dive into Fine-Grained Reactivity and the future of Signals
06mEmbracing Reactivity: Signals Unveiled in Modern Web Frameworks
19mAngular Signals: A Look Under the Hood and Beyond