Signals: What, How, and Why!
summary
Argues that signals are a push-pull signals implementation that yields fine‑grain reactivity by updating only getters instead of re‑rendering whole components, and that this avoids intermediate state glitches while remaining efficient. Compares React re-rendering to Solid’s eager model and Zelt’s lazy model using live code and console logs to show lazy scheduling causes console lag whereas Solid’s eager updates show immediate, correct values. Notes Solid’s hybrid scheduler and a working demo and compiler optimizations.
AI-written summary · about
chapters (14)
- 0:00Introduction to signals
- 1:33Worked with signals?
- 2:39API architectures & reactivity
- 5:53Push-pull model & React
- 7:20Fine-grained reactivity needs
- 9:26Fine-grained without push-pull
- 11:14React vs Solid code
- 14:12Golden rule of reactivity
- 14:53Lazy vs eager signals
- 18:05Solid’s reactive system
- 21:14Why Solid uses eager
- 22:37Debugging signals
- 25:03Memory vs performance
- 27:37Solid Hack & closing
