I feel like React hooks even though they provide a concise way to write code. they pushed react 2 decades back. classes had provided a standardized way to do stuff in React land. Now you're going to have places where people use hooks, others classes. n in my personal experience will result in different testing strategies n unknown bugs. this is one of the reasons, I quit working as frontend software engineer. just too much change
How do you push a 6 year old piece of software 2 decades back? I know you're exaggerating, but after admitting that you don't work with front end anymore (so I'm assuming you haven't really worked with hooks for very long) it's hard to understand why your opinion is of value here.
I've been working with React for 3+ years now and hooks are a major step forward in terms of both productivity and writing clean, efficient, reusable code. Anyone who spends some time wrapping their head around hooks realizes this and from what I see, a large majority of react / react-native library developers are on board as well.
Hooks can be adopted and implemented gradually along side class based components without issue, and no one has trouble when both exist along side each other. There is no rift in the react community because of this, and to suggest there is just reveals your ignorance, it's only pushing things forward.
it wasn't meant to be literal. '2 decades back' as a metaphor. hooks after all are just closures. so yeah I understand them. but that's not the problem. the issue is having two competing ways of doing things. look at rails they standardized the way of doing things way back and they haven't changed. & hence why a lot of rails people are productive
I like the fact that you said "2 decades back" and then in the same breath you said "classes had provided a standardized way to do stuff in React land." Did you know that classes weren't the original way to do things in React land because JavaScript didn't have them? You'd use React's own version using React.createClass instead. For the longest time there were people against the introduction of classes in JavaScript because it obscured JavaScript's prototypal inheritance nature and they stuck to React.createClass and lamented that "class Foo extends React.Component" was too much divergence from React.createClass and made things inconsistent.
