Front-end fatigue has a way of producing resignation letters. Asko Nõmm wrote that the joy is gone: he does not want to spend his nights reading up on "some new flavour of *.js" for fear of becoming irrelevant, does not want to learn "a million different tools," and does not want to know "a bit about everything and a lot about nothing." He backed the sentiment with action, resigning from his job to pursue an exclusively back-end role.

The complaint is familiar enough that it rarely goes a day without an airing. Whether back end is meaningfully better on technology churn is debatable, but it is discussed less.

The case that the problem is self-inflicted

Remy Sharp, in The web didn't change; you did, argues that front-end work is not harder or more complicated in itself — developers made it that way. Nõmm's own account concedes a related point: any simplicity you feel nostalgic for is still present on the web, and nothing prevents you from using it, except a client or boss who does.

That pushback matters, since many developers have no say in the stack they are handed.

Plain HTML as a viable target

Marc (surname deliberately kept off the internet) notes that hand-written HTML never went away despite growing pressure to treat frameworks as the only way to build for the web, and calls it a perfectly suitable way to build a personal site. Steren Giannini has described building websites with HTML alone and no build process at all. Terence Eden has made the case for simple HTML's "unreasonable effectiveness," particularly for public services and systems people reach when they urgently need help: plain HTML works, a bit of CSS makes it presentable, JavaScript is probably unnecessary though useful for progressive enhancement, and alt text on images helps people paying per MB as well as accessibility.

Important sites can thus avoid heavy complexity and still do their job.

Choosing a level of complexity deliberately

There is a middle position between abandoning front end and submitting to every new tool. The ecosystem is not inherently hostile; the useful skill is treating complexity as a trade. Lean into it when it buys speed, features or developer experience, and understand what it costs you and your users, and why. Step back from it when it doesn't.

CSS-Tricks star logo