Q&A with Angular team on 2.0, AtScript & more
summary
Roadmap and concrete choices matter: Angular 1.3 stays supported for 1½–2 years after 2.0, IE8 support is dropped (1.2 keeps it), and the new router is released as a separate module/repo — yes it’s coming. Shadow DOM lands in 2.0 with Shadow DOM emulation already working in AngularDart. Tooling: start writing ES6 now via Traceur (arrow functions, classes, modules). Change detection favors optimized dirty checking — roughly 20,000 dirty checks per ms — and zones remove explicit $apply.
AI-written summary · about
chapters (32)
- 0:00Angular 2.0 long-term support
- 1:03IE 8 support future browsers
- 3:58Mobile focus legacy browsers
- 6:03ngMessages vs ngSwitch
- 8:43AtScript vs Dart TypeScript
- 11:31Codebase prep for 2.0
- 13:41Angular 2.0 release timeline
- 15:06ES6 shims in libraries
- 16:09Angular TypeScript fork
- 17:32Migration tools dual support
- 18:39JS rendering for SEO
- 19:21Server-side rendering isomorphic
- 20:46Scope apply in 2.0
- 21:48Dirty checking vs Object.observe
- 25:24Two-way binding in 2.0
- 26:302 to 1.3 migration
- 27:11Lazy loading large apps
- 27:56Package management 2.0
- 29:44Accessibility ARIA roles
- 31:34Google’s Angular commitment
- 32:36Accessibility testing Protractor
- 34:26Angular Material framework
- 36:56Material Design user research
- 39:05Material Design research
- 40:08Screenshot testing UI
- 41:58AngularDart vs AngularJS
- 42:38Angular certification plans
- 44:02Dart’s future language
- 46:14Localization i18n support
- 47:40Google’s Angular products
- 49:07Google services integration
- 50:52Closing remarks and team appreciation
