Chrome ❤️ ⚛️ (no, really)

on YouTube ↗24m

" summary

Chrome adds a frameworks PM and prototypes an in-browser scheduler called the postTask API prototype to avoid long tasks blocking input and the uncanny valley where pixels appear but interaction lags. React and Next collaboration yields concrete wins: meta frameworks produce 16–17.3% faster sites in tests (Nuxt wrapping Vue cited), PRs landed for modern.js and bundle chunking, and metrics show the problematic gap between FCP and TTI given the 10–50 ms responsiveness target; prototype is live and wants feedback.

AI-written summary · about

" chapters (11)

1. 0:00Introduction
2. 1:23Frameworks as web platform
3. 3:36Collaboration with React
4. 8:50Frameworks driving performance
5. 13:10Keeping UI responsive
6. 16:56In-browser scheduler with React
7. 17:22Metrics missing UX
8. 19:11Fast initial load
9. 20:27Meta frameworks as infrastructure
10. 21:56Investing in Next.js
11. 23:05Call for collaboration

" related talks

• 26mClosing KeynoteNicole Sullivan · EmberConf 2020
• 42mElevating the Web Platform with the JavaScript Framework CommunityNicole Sullivan, Shubhie Panicker · Google I/O 2019
• 37mRuntime Scheduling on the WebShubhie Panicker · #PerfMatters Conference 2019
• 43mCreating instant and seamless web apps with ChromeShunya Shishido, Hadyan Andika · Google I/O 2022
• 39mWhat’s new in performance?Katie Hempenius · performance.now() 2022
• 21mBringing Excellent UX to the React Ecosystem via Strong Defaults in Next.jsShubhie Panicker, Houssein Djirden · Next.js Conf 2020
• 40mWhat’s New with Chrome and the WebBen Galbraith, Dion Almaer, Paul Lewis, Barb Palser, Dana Ritter · Google I/O 2019
• 41mReact - Rethinking Best Practices (updated)Pete Hunt · JSConf.Asia 2013