Can you imagine a future without zones?
summary
Zone.js is not part of change detection but Zone.js triggers change detection by patching async events; disabling it demonstrates that Angular needs extra wiring to run change detection. Manual APIs work: ChangeDetectorRef.detectChanges runs immediately (five calls produce five cycles), while Ivy’s markDirty schedules one VM-turn cycle and batches updates. Trade-offs are concrete: +automatic detection vs −20–50KB bundle size, slower startup from patches, noisy runs for high-frequency events, and harder debugging; ngRx-style connect could provide semi-automatic, explicit updates.
AI-written summary · about
chapters (6)
- 0:00Start
- 12:51Manual change detection
- 15:11Manual charge detection in Ivy
- 17:10Using event handlers
- 17:58The need for an escape hatch
- 21:43Change detection strategies
related talks
31mCan you imagine a future without zones?
01h 02mChange Detection, Zone.js and Other Monsters
41mState of change detection in Angular and how far are we from Zoneless applications ?
44mAngular 2 Change Detection Explained
33mAngular 2 change detection explained
30mNo Zone, No Problem - Building Angular Apps without Zone.js
46mAngular 2 Change Detection Explained
19mThe Magic and Mystery of Angular Change Detection