Does Progressive Enhancement Have a Place in Today's Web?
summary
Claim: progressive enhancement remains useful because building from start with HTML and then layer on CSS and JS lets teams ship a server-rendered HTML/CSS baseline, iterate cheaply, and add Ajax/WebSockets or service workers only where inherent complexity demands it. Concrete notes: service workers are only in Chrome and Firefox today, Ghostery/privacy blocks can break analytics, the UK government measured 0.9% JavaScript enabled but never ran. Use server rendering for Medium-like reading, single-page apps for Slack-like real-time needs.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 0:24What is progressive enhancement
- 8:04Single page apps explained
- 14:09Complexity in web apps
- 18:24Progressive enhancement benefits
- 21:15Choosing the right approach
- 26:13JavaScript use and caution
- 27:39Q&A
