## Summary Popular JavaScript frameworks market themselves on developer experience (DX) but often ship poor user experience (UX). The author argues the answer isn't to abandon DX, but to redirect it toward enabling developers to deliver reliable, first-rate UX. The recommended path is the web platform and web standards, which have been proven over decades and offer powerful techniques for great user experiences. Shifting focus this way would itself be an exciting developer experience. ## Key Points - DX is how easy it is for a developer to do the essential tasks needed to implement a change; good DX makes those tasks relatively easy for the team. - Good DX products tend to be easy to learn, efficient, consistent, transparent, and resilient. - Framework-driven DX often correlates with worse UX, not better. - Contemporary DX distorts developer education: curricula chase React and similar tools while glossing over HTML, CSS, HTTP, browser APIs, semantics, and accessibility. - The result is early-career developers fluent in framework concepts but missing foundational web knowledge, failed by an industry chasing the new and shiny. - Web standards have existed for decades and can deliver exceptional UX; wider adoption pushes them forward. ## Claim Atoms - **Good DX often produces bad UX** — frameworks sell DX yet ship poor end-user experiences. - **DX warps education toward shiny tools** — fundamentals like HTML semantics and accessibility get skipped for job-friendly frameworks. ## Links - Connects to the broader web-standards-over-frameworks argument and to developer-education critiques about foundational web skills being neglected. - [[3. Resources/MOCs/DevRel MOC]] — applies-in: the MOC lists this note under Developer Experience (DX).