Evolution Of The Web
summary
Explains how web standards actually change: the W3C uses community groups → working groups → candidate recommendation with implementer testing, the IETF publishes RFCs and runs three meetings a year with one per continent and even hum voting for consensus in rooms, and specs move to editable repos where you can use GitHub pull requests; gives concrete numbers (WebRTC group lists about 88 registered and only 10–15 driving decisions), notes HTTP/2 as an example, and flags Singapore hosting IETF next year.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:49Evolution of the web
- 2:03Who are we?
- 6:06Web Is Not Internet
- 8:05Who made the Internet and the Web?
- 12:40How are standards enforced?
- 14:55The Nerd Force
- 17:37Internet: Nerds at IETF
- 23:17Web: Nerds at W3C
- 23:49Creating standards at W3C
- 26:07Official standards process
- 27:02Unofficial, real process
- 27:56Google, Mozilla, Microsoft, and Apple Know Best
- 28:57We NEED more developers
- 30:16Where to go
related talks
17mEverything You Always Wanted to Know About Web Standards
31mThe Web is Changing the World. Are you READY?
30mEnabling Web Developers to Build the Future of the Web
24mHitchhiker's Guide to Web Standards
34mPanel: Don't Break the Web! - Evolving JS While Keeping Developers Sane
43mPanel Discussion: How Web Developers are Changing Web...
32m📗 Web standard consortiums are a game with Chrome as the monopoly man
48mLayers of the Web