undefined | Better HN

0 pointsviklove6y ago0 comments

> In the long term, change wins. Or else we'd be programming in JS1995.

Change for the sake of change is not a sound argument.

The thing about hooks is they don't enable a single thing we couldn't already do with HOCs. They are also much harder to read, because stateful logic is now just sprinkled around your render method rather than being isolated to places you know to look for it. I won't be using hooks ever, as far as I'm concerned.

0 comments

pacala6y ago

Of course.

* "A Critique of React Hooks"

* "A Critique of the Change Costs Induced by React Hooks".

Objections to React Hooks are stronger if they don't invoke change costs as the primary three concerns.

runawaybottle6y ago

He/she gave a very valid critique of state being jammed into your render method, vs state being handled in a predictable pattern in Class components.

And lastly, let’s not minimize change-cost. In the real world, it’s a cost. We’re all willing to pay it if it’s necessary, or affordable, but not because someone showed up and said ‘change please’.

j / k navigate · click thread line to collapse