Browser Native Web Development: No Frameworks, Just the Browser
summary
Claims concrete enough to act on: Netflix removes React from its landing page and records a 50% improvement in time‑to‑interactive; GitHub drops jQuery and implements the same features using standard browser APIs; SpaceX Dragon displays run on Chromium with HTML/CSS/JS and web components. Data: Web Almanac shows jQuery ~80% market share, React ~8% (W3Tech: jQuery 77%, React 4%); core.js ~35M weekly downloads; average homepage has 55.6 images and only ~59% include alt text. Use Lighthouse accessibility checks and semantic HTML to improve SEO and accessibility.
AI-written summary · about
chapters (17)
- 0:00Introduction and challenge
- 1:25Apollo vs SpaceX capsules
- 4:58Netflix dropping React
- 5:19GitHub removing jQuery
- 6:20Web Almanac insights
- 9:09jQuery and browser APIs
- 15:21Switching to examples
- 16:26Bread recipe in HTML
- 23:13Semantic HTML benefits
- 26:32Accessibility with headers
- 33:02Divs vs semantic elements
- 33:45Image alt text importance
- 35:11Google Lighthouse demo
- 40:12HTML elements accessibility
- 46:16Alt text for SEO
- 47:21Web Almanac findings
- 48:28Summary and conclusion
related talks
42mElevating the Web Platform with the JavaScript Framework Community
41mYou Really Don't Need All That JavaScript I Promise
26mLess Cruft, More Power: Leverage the Power of the Web Platform
40mDid We(b Development) Lose the Right Direction?
26mClosing Keynote
39mYou really don't need all that JavaScript, I promise
22mHTML: How to Make Loveliness
58mKeynote: Where Web Tech is Going Now