4 ms·
React doesn't change frequently though, that's the point. And it has always had excellent backwards compatibility. Class components are still fully supported, f
by frosted-flakes 4y ago
React doesn't change frequently though, that's the point. And it has always had excellent backwards compatibility. Class components are still fully supported, for example.
- ipaddr 4y agoReact changes best practices every few years prompting many rewrites.
- forgetfreeman 4y agoOne has to question the sanity of a rewrite launched for the sake of notional orthodoxy. If it ain't broke...
- AlwaysRock 4y agoRight but you dont actually have to rewrite it, correct? The updates dont break the old code. It's just not best practice anymore.
- addicted 4y agoReact changing best practices every few years is a good thing! It means it keeps getting better. That would be a bad thing if it meant that earlier best practices were no longer maintained. But that’s not true. Class components are still around. All official documentation continues to have class component examples and explanations (where it makes sense obviously…there isn’t any class component documentation under hooks, of course). And class components will likely still be around 5 years from now.