Reactive Angular. At its core.
summary
Angular plans to bake reactive primitives into the framework using signals (boxes with synchronous values) and computed derived values, with a demo implementation checked into the repo and a public RFC already receiving ~650 comments. The claim is concrete: templates will read signals directly, enabling per-component change detection, making Zones optional, and turning inputs and some APIs into signal-backed values. Timeline: a signal library appears around v16 and deeper integration lands around v17.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 5:18Reactive Angular meaning
- 8:07Signals as boxes
- 10:36Computed signals
- 13:27Signals in components
- 18:36Angular reactivity future
- 24:12Signals benefits
- 27:23Framework improvements
- 28:48RFC announcement
- 31:19Next steps
- 33:05Live code demo
related talks
32mEverything you need to know about Angular Signals
51mSignals in Angular: How Do They Work?
46mThe Future of Angular: Faster, Lighter, Stronger
31mThe Angular Reactivity Momentum in a Nutshell
26mGo Reactive with Angular Signals
29mThe Angular Renaissance
24mAngular Architecture using Signals
32mOpening Keynote: The State of Angular