Another day, another email documenting a vast waste of resources on a React upgrade.

You know who doesn't have to do this nonsense? Folks who write to the web platform. Your old code still works. Your new code works even better.

Why? Because unlike React, we take the platform's role *as a platform* quite seriously.

If your org is trapped on the treadmill[1], you should plan One Last Upgrade: get to React 19 (which *finally* has Web Components support) -- or even better, Preact -- then *get the hell off*. Move your componentry to WC incrementally, bit by bit, until the React part of your codebase is nothing more than`<><web-component-app></web-component-app></>`

[1]: https://polotek.net/posts/the-frontend-treadmill/

The Frontend Treadmill

A lot of frontend teams are very convinced that rewriting their frontend will lead to the promised land. And I am the bearer of bad tidings. If you are building a product that you hope has longevity, your frontend framework is the least interesting technical decision for you to make. And all of the time you spend arguing about it is wasted energy. I will die on this hill.

@slightlyoff We're doing this approach; converting our DS to Web Components and archiving our React and Vue DS components. In paralell upgrading React to 19 across the org. Then we provide React wrappers for existing React apps (limit cost of adoption) and engourage non-wrapped Web Components in new apps. We have one setup for React and on setup for progressive enhancement. Then run education on progressive enhancement and standards.