Angular Signals: What's All the Fuss About?
summary
Signals deliver concrete tradeoffs: synchronous glitch-free synchronization of state with computed signals and effects, a push‑pull update protocol, and simpler templates; converting an example cart service drops from 87 to 57 lines and removes many async pipes. Signals handle local UI state (form validity, router params) while observables keep streaming async work (HTTP, events). RxJs interoperability exists so signals augment not replace RxJs, and the demo conversions work and improve clarity and performance.
AI-written summary · about
chapters (14)
- 0:00Angular Signals intro
- 1:47Why Angular adopted Signals
- 4:20What makes a framework reactive
- 9:26Signals: what and how
- 15:41Signals vs Observables
- 19:39Signals examples in Angular
- 24:44Final thoughts on Signals
- 26:45Q&A
- 29:17Signals in effects and computed
- 31:29Learning curve and future
- 36:09Glitch-free properties and async
- 37:16Signals with Nx and NgRx
- 37:39Best practices for Signals
- 40:09Closing remarks
related talks
19mAngular Signals: A Look Under the Hood and Beyond
24mAngular Architecture using Signals
36mEffective Signals in Angular 19 and above: Rules and Helpers
28mHow Signals shape a Pull-based architecture
32mEverything you need to know about Angular Signals
20mAngular Signals under the Hood
14mAngular w Signals
51mSignals in Angular: How Do They Work?