State of change detection in Angular and how far are we from Zoneless applications ?
summary
Explains that Angular now uses Signals-based local change detection to build a signal graph so the framework only re-renders nodes that actually changed, eliminating many ancestor traversals, preventing ExpressionChangedAfterItHasBeenChecked errors and allowing bidirectional updates without manual microtask hacks. Shows a live demo that highlights far fewer change detections. Describes a zoneless scheduler using rAF+setTimeout prototype that replaces Zone.js (removing ~30 KB and noisy stack frames), and notes ongoing work on stability/hydration APIs and v17 hooks; the prototype works but full zoneless apps remain in progress.
AI-written summary · about
chapters (11)
- 0:00Angular change detection intro
- 5:03Zone.js and scheduling
- 10:28OnPush optimization
- 13:51Bidirectional data flow fixes
- 17:23Signals for state
- 21:41OnPush vs Signals challenges
- 25:20Signal-based improvements
- 30:44Moving beyond Zone.js with zoneless apps
- 35:49Zoneless challenges
- 39:49Future of change detection
- 40:12Q&A
related talks
37mGet ready to go Zoneless
30mNo Zone, No Problem - Building Angular Apps without Zone.js
44mAngular 2 Change Detection Explained
44mThe Future of Angular: Faster, Lighter, Stronger
01h 02mChange Detection, Zone.js and Other Monsters
40mThe Future of Angular: Faster, Lighter, Stronger
25mCan you imagine a future without zones?
19mThe Magic and Mystery of Angular Change Detection
