A Quest to Be a (Web)master: How do You Go from Simple Code to Building Great Web Experience?
summary
Argues that knowing browser internals — CPU vs GPU, processes and threads, the DOM→layout→paint→composite pipeline — changes choices and fixes real bugs; demonstrates Chrome-based tooling like service worker startup and navigation preload, inspects compositor thread and tile rasterization, runs Lighthouse audits, and uses feature-policy headers. Shows a small image-visualizer app and multiple knitting apps (five plus), reports keeping 48 tabs of references, and explains what actually sped up rendering and what didn’t.
AI-written summary · about
chapters (9)
- 0:00Start
- 6:26How To Be a Web Master
- 11:41What the Browser Is Process and Threads Look like
- 14:48Multiple Lender Processes for Chrome
- 18:56Safe Browsing Check
- 20:52Introduction of Service Worker
- 26:29Is It Possible To Render the Page
- 36:51Lighthouse
- 37:27Feature Policy
related talks
44mAiming for the Stars
37mHappy Browser, Happy User!
50mThe Browser is a Marvelous Thing
29mThe Road to Web Performance in 3 Critical Steps
50mRocking Out with Browser-Based Developer tools
47mEvaluating Technology
44mAdvancing the web without breaking it?
45mThe Browser Is Not a Flux Capacitor, and You Know It... Or Do You?