Progressive Enhancement

on YouTube ↗51m

" summary

A survey of 800 developers shows 25% of 800 see progressive enhancement as “works without JavaScript.” Examples include talky.io and SVG OMG losing core function with JS disabled, and Facebook building a custom mobile site for Japan because HTML/CSS support is incomplete. The panel pins a real problem on ES2015 syntax breaking old engines, the practical reliance on Babel or dual bundles, brittle feature detection despite CSS.supports, and real-world performance traps like 52 KB whiteout and the push toward service workers/offline-first.

AI-written summary · about

" chapters (6)

1. 0:00Start
2. 4:37each phase of the enhancement needs a user
3. 5:13figuring out what is core functionality and what is an enhancement.
4. 5:40What is the JS framework story?
5. 6:12Web Components
6. 9:18Is there a workflow that solves this?

" related talks

• 30mDoes Progressive Enhancement Have a Place in Today's Web?George Brocklehurst · WindyCityRails 2016
• 44mEnhance!Jeremy Keith · beyond tellerrand Düsseldorf 2015
• 01h 13mFOUC, and the Death of Progressive EnhancementKyle Simpson · You Gotta Love Frontend 2019
• 34mWeb development isn't about you, dudeCharlie Owen · CSSConf Budapest 2017
• 01h 10mFOUC and the Death of Progressive EnhancementKyle Simpson · JSCamp Barcelona 2019
• 39mYou really don't need all that JavaScript, I promiseStuart Langridge · JSCamp Romania 2019
• 17mSimplicity panelUna Kravets, Juho Vepsäläinen · Future Frontend 2026
• 51mThe Business Of Front-End DevelopmentRachel Andrew · Full Stack Fest 2015