Are Signals worth the hype?
summary
Claims that signals give a clearer mental model for rendering UIs and make apps more predictable and less error prone while performance wins are a bonus, backed by a live counter demo that shows counter demo showing only changed nodes re render and comparisons across frameworks (Solid, Vue, Angular, React) plus TC39 stage one. Explains implementations: Solid eager implementation versus lazy approaches that avoid the diamond glitch, frames signals as a push then pull model with tradeoffs in memory and concurrency.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:49What are signals
- 5:24Push vs pull reactivity
- 10:13Demo fine-grained reactivity
- 13:52Why signals matter
- 15:18Debugging with signals
- 20:12TC39 proposal impact
- 23:08Eager vs lazy signals
- 27:52Framework landscape
- 28:57Signals worth the hype
- 29:19Q&A
related talks
52mIt's Time To Talk About Signals
28mSignals: What, How, and Why!
48mJS Signals
06mEmbracing Reactivity: Signals Unveiled in Modern Web Frameworks
27mA Deep Dive into Fine-Grained Reactivity and the future of Signals
21mUnderstanding Rendering Patterns
19mAngular Signals: A Look Under the Hood and Beyond
28mHow Signals shape a Pull-based architecture