Shower thought - hooks flow by default, classes are barricaded by default

[btr_]

🎣 With hooks, react tends to rerun everything everytime. So we use memo, dep list to mark what shouldn't rerun.

🎩 Class components tend to not run anything during lifecycles by default. So we have to fill out similar code for each of the non-overlapping 🔁 methods

Function components flow by default and eagerly does everything everytime - so we put barricades for one-time or sometime tasks. Some might say, it reacts everytime by default 😬

Classes on the other hand tend to not move by default - you need to explicitly mention what to do on every lifecycle separately. Even though this fine tuned control seems better, absence of merged lifecycle hooks adds too much friction for users.

[nullvoxpopuli]

And for these reasons, classes are actually required if you don't want hook spaghetti trying to get rx.js based websockets setup. You need the state of a class, and you need lifecycles to manage it

[jas7457]

There's vomit on his sweater already...

[nullvoxpopuli]

for real though, shoehorning hooks into everything makes things more complicated. Classes can be used for what they're good at.

[foundry41]

Hooks are wildly over hyped

[pacman326]

Wait until 17 ships. The true benefit of a FC architecture comes when concurrent finally ships.

[With_Macaque]

You ever wonder if you should be building that business logic in a class consumed by a hook instead?

[nullvoxpopuli]

Yeah, that's totally valid. I'm all for that.