Elevating the Web Platform with the JavaScript Framework Community
summary
Chrome describes concrete collaborations with frameworks: a browser scheduler prototype plus the shipped isInputPending API and a display locking primitive, React and Vue experimenting with yielding and schedulers, and a tiny bootstrap (under 47 kilobytes) that queues early clicks with jsaction and a dispatcher. Goals include a 170kb budget for initial route code via component-level late loading, module/nomodule differential loading, and a package.json proposal to publish modern JS to cut polyfills and duplication.
AI-written summary · about
chapters (15)
- 0:00Collaboration and vision
- 3:24Improving UI responsiveness
- 7:15In-browser scheduling
- 9:19New APIs for performance
- 10:59Nuance in performance goals
- 12:33Incremental loading strategy
- 14:06Production battle-testing
- 18:29Interaction-driven loading
- 22:28Smart server-side rendering
- 27:39Scalable app architecture
- 30:26Framework ecosystem role
- 31:31The state of web performance
- 33:49Tackling dependency bloat
- 37:21Future of JS delivery
- 40:00Conclusion and call to action
related talks
24mChrome ❤️ ⚛️ (no, really)
26mClosing Keynote
43mFrameworks and the Future of the Web Platform
49mBrowser Native Web Development: No Frameworks, Just the Browser
37mRuntime Scheduling on the Web
42mThe Good, The Bad, The Web Components
45mNo framework frontends in practice - use the platform!
31mWhat's new for the web platform