> Markdown version of [/videos/287-state-of-angular?t=2195](https://www.wearedevelopers.com/videos/287-state-of-angular?t=2195). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# State of Angular

Legacy IE11 support is finally dead. Angular v13 enforces the Ivy engine to drastically reduce enterprise build times. Learn how standalone components will transform your future app architecture.

- **Speakers:** Jessica Janiuk
- **Event:** JavaScript Congress
- **Published:** November 23, 2021
- **Duration:** 41:34
- **URL:** https://www.wearedevelopers.com/videos/287-state-of-angular

## Summary

The Angular framework continues to evolve through deep integration and validation within Google's own ecosystem, driving significant performance and developer experience improvements. A major milestone in this journey is the complete rollout of the Ivy rendering engine, which yielded a 90% reduction in computational resources and drastically reduced build times for large-scale enterprise applications. This internal validation directly benefits the open-source community, ensuring that Angular remains a robust, scalable platform supported by rich collaborations with teams like Firebase and TensorFlow for advanced infrastructure features like predictive prefetching.

With the release of Angular v13, the framework enforces Ivy as the sole renderer and definitively drops legacy Internet Explorer 11 support. This strategic deprecation unlocks the ability to leverage modern web standards, including native CSS variables, intersection observers, and modern ECMAScript features, fundamentally streamlining the core architecture. Furthermore, the Angular team has prioritized community responsiveness through dedicated triage workflows to eliminate issue backlogs, while introducing structural developer extensions like Angular DevTools for enhanced profiling and improved error code visibility to simplify debugging complex lifecycle events.

Looking toward the future, the framework is moving toward a more streamlined developer experience highlighted by the introduction of standalone components. By proposing a shift away from mandatory NgModules, Angular aims to reduce learning curves and architectural complexity, allowing developers to treat components as independent building blocks with built-in lazy loading capabilities. Coupled with upcoming extended template analysis and ongoing efforts to optionally decouple Zone.js for change detection, Angular's public roadmap emphasizes both strict backward compatibility and continuous modernization, ensuring stability while embracing the broader web framework ecosystem's modular innovations.

**Keywords:** angular v13 release, ivy rendering engine, standalone components architecture, ngmodule mental model, zone.js change detection, angular devtools profiling, legacy browser deprecation, enterprise web framework scaling, protractor testing migration, webpack 5 caching, extended template analysis, predictive prefetching performance, material design accessibility, component lazy loading

## Chapters

1. **Core principles of the Angular framework** (00:02) — Why Angular remains a stable, scalable, and opinionated platform built specifically for web development.
1. **How Google collaborates and validates Angular** (01:16) — The core teams leverage internal Google projects to heavily validate and support the framework.
1. **Framework integrations with Firebase and TensorFlow JS** (02:40) — Collaborations with adjacent Google teams produce powerful capabilities like predictive prefetching for e-commerce.
1. **Developing and launching the Ivy renderer** (05:13) — Two years of development produced a smaller window of code and fundamentally improved rendering speeds.
1. **Internal developer productivity wins from Ivy** (07:38) — Transitioning to Ivy reduced Google's computational resources and significantly shaved off internal build times.
1. **Debugging with the Angular DevTools extension** (08:51) — A highly requested Chrome extension provides deeper application profiling and clarifies complex framework errors.
1. **Establishing clarity with a public roadmap** (10:36) — A public roadmap gives external developers and enterprises confidence in the future direction of the framework.
1. **Triaging issues and prioritizing feature requests** (11:52) — Dedicated bots and focused triage efforts drastically reduced outstanding pull requests and improved community responsiveness.
1. **Breaking changes and features in version 13** (15:44) — The latest release removes legacy Internet Explorer support to fully leverage modern ECMAScript interfaces.
1. **Improving build flows and component accessibility** (17:50) — The framework replaces its build optimizer with Babel and upgrades material components for improved accessibility standards.
1. **Preventing bugs with extended template analysis** (19:29) — Upcoming tooling acts like a linter for templates to intercept syntax errors within standard code editors.
1. **Prototyping standalone components to reduce boilerplate** (20:39) — Overhauling the module system promises to simplify mental models by allowing components to exist independently.
1. **Embracing web framework competition as positive pressure** (24:34) — The maintainers view other tools in the JavaScript ecosystem as great sources of inspiration for standardizing best practices.
1. **Maintaining backward compatibility across major versions** (27:06) — Upgrades are designed to remain seamless without forcing painful migrations like the transition away from AngularJS.
1. **Transitioning toward modern end-to-end testing tools** (28:59) — The deprecation of Protractor opens the door for developers to integrate their preferred external testing solutions.
1. **Code splitting and lazy loading standalone components** (31:40) — Engineers will retain identical dynamic capabilities without maintaining the overhead of complex modules.
1. **Navigating future goals to make Zone optional** (33:38) — Untangling change detection to operate without its traditional abstraction layer requires significant architectural planning.
1. **Identifying practical applications for standalone components** (35:17) — Isolated page components no longer require wrapping constructs unless specifically building bundled component libraries.
1. **Implementing predictive prefetch with machine learning** (36:35) — Cross-team efforts highlight performance wins through external talks covering real-world client-side machine learning.
1. **Considering virtual DOM adoption within Angular** (37:33) — Fundamental rendering rewrites are highly unlikely given the massive investment to mature the current compiler.
1. **Resolving dependencies directly inside standalone views** (39:14) — Current decorators will ingest routing and directive references to retain dependency injection features per component.

## Related Moments

- [Exploring Angular component patterns and upcoming framework updates](https://www.wearedevelopers.com/videos/364-angular-tips-tricks-you-can-use-from-tomorrow-on) (from "Angular tips/tricks you can use from tomorrow on")
- [Evolution of the Angular framework from AngularJS](https://www.wearedevelopers.com/videos/656-stand-alone-components-in-angular) (from "Stand alone components in Angular")
- [Overview of the Angular development platform](https://www.wearedevelopers.com/videos/189-angular-angular-cdk-awesomeness-combined) (from "Angular <> Angular CDK - Awesomeness Combined")
- [Evolution and benefits of the Angular ecosystem](https://www.wearedevelopers.com/videos/197-angular-features-you-should-be-using) (from "Angular Features You Should be Using")
- [Evaluating the long-term trajectory of the Angular framework](https://www.wearedevelopers.com/videos/317-differential-loading) (from "Differential Loading")
- [Implementing standalone APIs in modern Angular architectures](https://www.wearedevelopers.com/videos/656-stand-alone-components-in-angular) (from "Stand alone components in Angular")

## Related Articles

- [The Best JavaScript Framework to Learn](https://www.wearedevelopers.com/magazine/229-the-best-javascript-framework-to-learn)
- [Dev Digest 222: Google's Web Future, AI Profitability & Centering DIVs](https://www.wearedevelopers.com/magazine/737-dev-digest-222-google-s-web-future-ai-profitability-centering-divs)
- [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix)
- [Web Development Best Practices: What The Data Tells us](https://www.wearedevelopers.com/magazine/84-web-development-best-practices-what-the-data-tells-us)

## Related Jobs

- [Senior Software Engineer, Angular (B2C Web Platform)](https://www.wearedevelopers.com/jobs/ext/1927757-senior-software-engineer-angular-b2c-web-platform) at **Bitpanda**
- [Software Engineer, React & Angular (Broker Web Platform](https://www.wearedevelopers.com/jobs/ext/1558399-software-engineer-react-angular-broker-web-platform) at **Bitpanda**
- [Junior Frontend Engineer](https://www.wearedevelopers.com/jobs/ext/1532351-junior-frontend-engineer) at **Almedia**
- [Staff Frontend Engineer](https://www.wearedevelopers.com/jobs/48313-staff-frontend-engineer) at **SMG Swiss Marketplace Group**
- [Software Engineer](https://www.wearedevelopers.com/jobs/ext/1377585-software-engineer) at **Bitpanda**
- [Senior Fullstack Engineer, Angular & Nestjs (Defi Wallet)](https://www.wearedevelopers.com/jobs/ext/1983681-senior-fullstack-engineer-angular-nestjs-defi-wallet) at **Bitpanda**