A single blog post about a broken healthcare site set off a chain of responses this week, and the thread running through them is the real cost of JavaScript frameworks — and what that cost says about how the industry weighs developer comfort against the people on the other end of the screen.

The blank screen at Modern Health

Eric Bailey's account is the starting point. Visiting a health service provider's site to book an appointment produced nothing but a blank screen. The site, Modern Health, ships its customer-facing experience in React and Webpack, alongside what Bailey describes as a terrifying amount of telemetry.

For anyone who builds for the web, the failure mode is easy to read: logic the site depends on for its whole experience collided with other errant logic it pulls in, producing a deadlock. For everyone else, there is only an endless fake loading spinner.

Bailey is blunt about why that distinction matters. Someone in a crisis does not care about TypeScript, tree shaking, hot module replacement, A/B tests, burndown charts, NPS, or OKRs — and developer experience counts for nothing if the person using what you built cannot get what they need.

The deeper problem is what happens when tooling and reporting, the very things meant to make teams more effective, end up standing between the user and the task. Blaming frameworks is divisive, but the Modern Health failure is less about React versus the framework of the moment and more about business priorities and developer experience colliding with user experience.

Russell: frameworks sold as lemons

Alex Russell picks up the argument in economic terms, and he does not soften it: partisans for slow, complex frameworks have marketed lemons as the hot new thing, and higher-quality options have been crowded out in the process.

These technologies were initially pitched on the back of "better user experiences", but have utterly failed to deliver on that promise outside of the high-management-maturity organisations in which they were born. Transplanted into the wider web, these new stacks have proven to be expensive duds.

The blame, in Russell's telling, lands less on developers than on how frameworks were sold to them. Once sellers embedded the idea that better Developer Experience leads to better user outcomes, improving DX became an end in itself, and many who knew better felt forced to play along. Long lead times before the trickle-down UX claims could be falsified worked in the sellers' favor — they do not need you to succeed, only to keep buying.

That framing is hard to hear, especially for anyone who has sunk time into a stack and wired it into their workflow. Settling on a toolchain resembles settling into a house; nobody wants to learn the foundation is sandy. It also helps to remember that plenty of developers do not choose their tools at all — managed teams are handed a stack — which is why the critique is about industry priorities rather than individual judgment.

Coyier: test with content blockers on

Chris Coyier moves from diagnosis to a concrete practice. Regardless of why an app runs on React, the work of making it reliable and accessible remains. One recurring way apps break is that blocking a single file takes the whole site down, typically because first-party JavaScript depends on third-party JavaScript that a blocker rejects.

If I block resources from tracking-website.com, now my first-party JavaScript is going to throw an error. JavaScript isn't chill. If an error is thrown, it doesn't execute more JavaScript further down in the file. If further down in that file is transitionToOnboarding();— that ain't gonna work.

Coyier's suggestion: run your end-to-end tests in browsers that have popular content blockers installed with default configs. That can surface failures of exactly this kind — the ones that stop customers, including people in need, before they ever reach what they came for.

The wider lesson is about how realistically an app's use is modeled, and how early. Understanding users — why they come, how they browse, where they are, what might get in their way — is information that should shape development decisions before they are made, not after an outage.

CSS-Tricks star logo

Sponsor CSS-Tricks!

We've got lots of ways to help you connect with the greatest front-end community in all the land.

CSS-Tricks Newsletter

Sign up to get front-end roundups, browser updates, and exclusive content sent to your inbox bi-weekly.

Ads are self-hosted