When JavaScript is Too Much: Using HTML and CSS Instead

You probably don’t need that component to be reactive.

JavaScript is powerful, but it is not a mandatory entrance fee for every interaction. HTML and CSS already solve more interface problems than we sometimes remember, usually with less code, better defaults and no loading spinner required.

CSS rewards people who understand its model more than people who accumulate workarounds. The cascade, intrinsic sizing and modern layout tools solve a surprising number of problems once we stop fighting them.

What makes this interesting is not the fashionable part. It is the effect on the person doing the work after the initial excitement has worn off.

Prefer the thing that survives contact

Front-end work has a habit of looking simple from a distance. The browser then introduces real content, small screens, old devices, keyboard navigation and somebody using the product in a way nobody drew in the design file.

That is why I favour choices that are easy to inspect. Start with semantic HTML, let CSS do the layout work it was designed for, and add JavaScript where it creates genuine value. Cleverness is occasionally useful; legibility is useful every day.

The best front-end code does not show off. It makes the interface feel obvious.

The web is wonderfully forgiving, but users should not have to rely on that forgiveness. Build from sturdy foundations and the interesting parts become much easier to enjoy.

The details will change from project to project. The underlying habit of paying attention travels well.