I’d hate to have to deal with incompatible versions at the rate they release major versions.
If you try to stick with one version do you soon get stuck because you need to take a bug fix or security fix that’s only available in a later major release (but updating breaks other things)?
I want to build software on a stable platform so I can spend time on improving the software or writing something new, not keeping up with updates.
React is stable, upgrading it is painless as long as you don’t ignore deprecation warnings. What can be annoying is other (abandoned) dependencies holding you back from upgrading.
What's the solution?
Maybe if you have a small app. React is as bad as going from angular to angular 2
You have no idea what you are talking about.
15 to 16 - pain.
16 to 17 - pain.
If you disagree you haven’t worked on anything even slightly complex.
Thankfully I’m on my 2nd project of ripping react out for htmx. The last one was a huge success. No doubt this one will be too.
The original `createClass` API was indeed deprecated and removed all the way back in 2017 [0]. You can still use them today with the separated `create-react-class` package.
ES6 class components still work as-is even in React 19 - it's just the legacy context feature that's been removed. They're generally discouraged, in that function components are now the standard way to use React, but they're still not "deprecated" in the sense of a warning or removal.
[0] https://legacy.reactjs.org/blog/2017/09/26/react-v16.0.html#...
Regarding class components in general, what is the problem with maintainers choosing to encourage devs to use their new APIs while keeping the old APIs working?
- https://macwright.com/2024/01/03/miffed-about-react
(looks like the author may have an HN-specific redirect, so you might need to copy-paste that URL)