The Angular Renaissance
summary
Shows concrete changes: Standalone Components (module-less apps, stable since v15) and how converting a single component works; introduces Signals as a built‑in reactivity primitive (demoed in StackBlitz with computed values and effects, warned not to misuse effects) and clarifies signals are not observables; explains template control flow with defer for lazy rendering and new if/else blocks; outlines migration path, opt‑in rollout, and the goal of removing Zone.js for faster, finer‑grained updates.
AI-written summary · about
chapters (15)
- 0:00Angular Renaissance welcome
- 1:05Humanist movement matters
- 2:29Angular 2.0 to innovation
- 3:56Three pillars of Renaissance
- 4:19What are Angular signals
- 10:21Live demo signals
- 13:36Anatomy of Angular signals
- 18:09When to use signals
- 20:14Standalone API explained
- 23:48Adopt Standalone components
- 24:50Why Standalone simplifies
- 25:33New control flow syntax
- 26:34Power of defer in templates
- 27:38Developer mindset pains
- 29:02Closing thoughts & Q&A
related talks
51mThe Angular Renaissance - Key New Features
21mBack in the game: Recent Revolutionary Changes in Angular
46mThe Future of Angular: Faster, Lighter, Stronger
44mThe Future of Angular: Faster, Lighter, Stronger
27mAngular Renaissance
51mUnleashing the power of Angular: Navigating the latest releases and transformations
43mThe New Angular
02h 47mAngular: The Renewal