The "Developer Experience" Bait-and-Switch - Infrequently Noted

We cannot continue to use as much JavaScript as is now normal and expect the web to flourish. At the same time, most developers experience no constraint on their use of JS...until it's too late. Lightweight, effective tools are here, but we're stuck in a rhetorical rut. We need to reset our conversation about 'developer experience' to factor in the asymmetric cost of JS.

TL;DR: We cannot continue to use as much JavaScript as is now normal and expect the web to flourish. At the same time, most developers experience no constraint on their use of JS…until it's too late. Lightweight, effective tools are here, but we're stuck in a rhetorical rut. We need to reset our conversation about "developer experience" to factor in the asymmetric cost of JS. JavaScript is the web's CO2. We need some of it, but too much puts the entire ecosystem at risk. Those who emit the most are furthest from suffering the consequences — until the ecosystem collapses. The web will not succe

related reading

• The new wave of Javascript web frameworksfrontendmastery.com
• Cognitive load is what mattersminds.md
• 7 Principles of Rich Web Applicationsrauchg.com
• The Market for Lemons - Infrequently Notedinfrequently.org
• The Performance Inequality Gap, 2023 - Infrequently Notedinfrequently.org
• The Great Gaslighting of the JavaScript Era | The Spicy Webspicyweb.dev
• The Descent — What Happened to the Frontend While You Weren't Watchingdavidpoblador.com
• Can You Afford It?: Real-world Web Performance Budgets - Infrequently Notedinfrequently.org
• The cost of convenience — surma.devsurma.dev
• Second-guessing the modern web - macwright.commacwright.com
• The quiet, pervasive devaluation of frontend - Josh Collinsworth blogjoshcollinsworth.com
• Navigating the future of frontendfrontendmastery.com