Closing Keynote
summary
Chrome adds a Frameworks PM, collaborates weekly with React to design a scheduler, and sunsets Polymer after poor adoption. Chrome reports a survey of over four million domains showing small perf differences between frameworks but big gaps between first paint and time-to-interactive. Contributions land in Next.js metrics and webpack bundle-size improvements, work with Microsoft on modern form controls, and Ember’s FastBoot and built-in metrics validate approaches in production.
AI-written summary · about
chapters (8)
- 0:00Start
- 5:07Max Barnett
- 11:54A Shared Goal
- 17:51Angular and Ember
- 18:20Why Should Chrome Invest in the Framework Ecosystem
- 20:19What Is Chrome Doing To Help
- 21:17Routing
- 21:42Conformance Tests
