Hacker News new | ask | show | jobs
by bern4444 2017 days ago
fair point haha and that's certainly where my personal bias plays a role. When I see something I don't understand I like to look for the reasoning behind it. Some google searching, talking to coworkers, and a bit more googling usually sends me down the right path to finding more information

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
2 comments
mgkimsal 2017 days ago
> When I see something I don't understand I like to look for the reasoning behind it.

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.

link
recursive 2017 days ago
The conclusion I came to is that some people are willing to put up with hooks if it means that they don't need to learn how classes and prototypes work. Maybe I'm wrong, but that's how it looks to me. Not all reasons are good reasons.
link
eyelidlessness 2016 days ago
This seems at least part of it. And you don’t even really have to learn those things to use stateful React class components, they’re very seldom deeply inherited or require any `this` besides lifecycle methods and their own implementation. Rendered components are not instances.

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.

link