Evaluating Technology
summary
Shows concrete evaluation criteria, demonstrates service workers fail well with cache and offline examples (Guardian crossword), inspects web components fail depending on use by comparing progressive enhancements versus whole-app polymer examples, measures tradeoffs like developer cost versus user benefit, points to specific APIs (Cache, Fetch, custom elements, Shadow DOM) and real outcomes (offline page, add‑to‑home on Chrome Android, broken experiences when assumptions are ignored), and gives actionable rules for when to adopt new web tech.
AI-written summary · about
chapters (18)
- 0:00Intro
- 2:30Evolution through Natural Selection
- 8:20Hardware Software
- 9:45Ubiquitous Computing
- 11:10World Wide Web
- 14:55Magic Elements
- 17:10How does it work
- 19:30Service Workers
- 22:10Service Workers Fail
- 23:30Web Components
- 24:20Ideal Web Components
- 26:10How well does it work
- 27:40The problem with web components
- 29:35Umbrella technologies
- 32:55Progressive web apps
- 35:25Who benefits
- 40:00Assumptions
- 44:35Technological Singularity
related talks
47mEvaluating Technology
01h 08mKeynote - Evaluating technology
43mResponsive, Adaptive and Responsible
46mFrontend development in the (current) future
44mDesign principles and implementation strategies for better offline experience
30mBuilding a better web for everyone
47mWeb Caching: Strategies, Pitfalls and Modern Tools
28mOut of the Shadows