The JavaScript We Never Questioned

We often reach for JavaScript because that's how we've learned to solve frontend problems. Need to calculate a layout value? Write a function. Need to coordinate styles across components? Add some logic. Need to handle a visual behavior? Start with an event listener.

Sometimes that's the right call. But sometimes we're writing JavaScript to work around a limitation that no longer exists.

CSS has evolved far beyond styling colors, spacing, and typography. Features like container queries, :has(), and modern layout capabilities have changed how we can approach problems that once required extra code.

The interesting part isn't that CSS can replace JavaScript. It can't, and it shouldn't try to. The real question is whether we're adding complexity because the problem demands it, or because we're still using an old solution out of habit.

In this article, I'll look at a few common frontend patterns, how modern CSS changes the equation, and where JavaScript still makes more sense.

The goal isn't to write less JavaScript just for the sake of it. It's to stop writing code that the platform can already handle.