Against framework fatigue

Every few months someone publishes a post titled something like “Is [Framework] Dead?” and a portion of the frontend community briefly loses its mind.

I used to participate in this. I don’t anymore.

What changed

I’ve been doing this long enough to have watched several frameworks go from “obviously the future” to “legacy concern” to “actually still fine for most things.” React, for a while, was the framework that was going to replace everything. Then Vue. Then Svelte. Each one arrived with a critique of what came before, and each critique was largely correct.

And yet: most of the web still works, most of the users don’t care, and most of the developers who learned the old framework are still employed.

The ecosystem moves fast at the edges. In practice, most production systems are running on something you would not call cutting edge. That’s not failure — that’s stability.

The thing I actually care about

I care about whether I can build what I need to build, at quality, without fighting my tools. That’s it.

I’ve done that in jQuery. I’ve done it in React. I’ve done it in Astro. The framework is a vehicle. Understanding the DOM, understanding CSS, understanding how browsers parse and render — that knowledge transfers. Framework-specific knowledge has a shorter half-life.

The posture I’ve landed on

Learn a new tool when it solves a problem I have, not because it’s generating conversation. Use boring choices in production. Keep a sandbox for curiosity.

The anxiety about staying current is usually anxiety about identity, not competence. You don’t need to be on the frontier of every tool to be good at your job. You need to be good at the things your job requires, and curious enough to keep learning.

That’s a slower kind of growth. It’s also more durable.