📗 Web standard consortiums are a game with Chrome as the monopoly man
summary
Argues that web standards stall because most browsers run on Chromium dominance so a single vendor effectively vetoes progress, cites 40% Google presence at W3C meetings and estimates it takes ~18 months of benchmarks, security audits and comment cycles to push a spec, calls out failed or compromised efforts like P3P, Do Not Track and patchy CSP rollouts, and proposes startups contribute even 30 minutes per month to change voting balance and speed practical, deployable standards.
AI-written summary · about
chapters (9)
- 0:00Introduction and disclaimer
- 1:45W3C standards landscape
- 4:51Chrome’s dominance in web standards
- 8:02Challenges in standardizing new specs
- 12:57Compromises and failed standards
- 15:47Tooling and participation issues
- 17:10Web consistency and safety concerns
- 19:14Call to action for startups
- 21:42Q&A session
related talks
48mWhose web is it anyway?
17mEverything You Always Wanted to Know About Web Standards
14mThe web ahead
43mResponsive, Adaptive and Responsible
19mThe journey towards corporate monopolies: The evolution of browsing
40mMoving Web Standards Forward, Faster
32mA Modern Web Landscape — Matt Biilmann, Frances Berriman, and Wilson Miner
21mLove the web for what it is