Clearly hooks are not a bad idea given how quickly they've caught on in the react/front end community too. So while the majority certainly isn't always right, there's usually a common reasoning worth understanding
Similar view here, to an extent. But... with many topics, a majority of what I find is fanboy posts that strawman "problems" with earlier tech/tools, gloss over problems with the new way, and fawn over "hello world" examples. It can take a lot of time to get deep reasons, that may have some impactful value on your own problem spaces, and... at some point, I have to draw the line on "investigating all the bandwagons".
But also, at some point, one of the reasons to adopt something is "everyone else is", and there's some value in using "the latest trend" (hiring, bug solving, new tools, etc). And that may be enough value, but rarely does anyone justify their decision with "everyone else is doing it" - they try to give deeper 'technical' reasons, when (whether there are good/strong reasons) sometimes they just aren't able to do a good job.
I know there’s an aversion to classes in a lot of the current React community but the Component design in React was really much easier to reason with.
