Fully Zone-less — High-Performance Angular Applications in Post IVY
summary
How to remove Zone.js from Angular apps to improve frame times by using template-level change detection with a push/change strategy, structural directives, and template caching to avoid redundant rerenders. Includes flame-chart analysis and explanations of microtask vs requestAnimationFrame scheduling, plus code snippets and a working proof-of-concept showing apps go from many frame drops per interaction to single-frame or none.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 2:37Talk agenda
- 4:46Ivy change detection
- 7:14Reactive state management
- 18:22Async pipe inefficiency
- 23:46Rendering strategies
- 29:14Scheduling and coalescing
- 37:09Forms and lazy loading
- 41:23New directives and templates
- 48:09Main thread scheduling
- 58:29Future plans
- 1:00:03Q&A
related talks
53mFully Zone-Less - High-Performance Angular applications in post IVY
30mFully ZoneLess High Performance Rendering in post IVY
23mPartially Zoneless Performance tuning without big bang refactoring
30mNo Zone, No Problem - Building Angular Apps without Zone.js
41mState of change detection in Angular and how far are we from Zoneless applications ?
37mGet ready to go Zoneless
44mThe Future of Angular: Faster, Lighter, Stronger
29mPartially Zoneless - Performance tunning without Big Bang Refactorings