Frontend

I see this and I raise it to the entire hooks system. React with classes was much better.

Fullstack devops at @vocdoni — votecaster.io & onvote.app

Ooh, spicy take. I disagree, though. Hooks let you abstract and reuse logic way more easily than HOCs. HOCs also came with their own foot guns.

I’m with you there, not that class based components were great but hooks failed to capture the abstraction they were downstream of and they added their own problems on top of that

@deandotland on twitter, grins.eth on everywhere else 🧹Janitor of https://innkeeper.link 💃Live music in /dcl every Tues/Thurs 

My point wasn't to defend classes, but to point that hooks weren't the best solution to that. So IMHO, both have their prons and cons, but the lifecycle in classes was a lot more logical than it is currently when you start adding multiple useEffect on a component.

constructor(props){
  super(props);
  this.state = ....
}

Was so clunky though

Open-source web3 dev. Prev CTO Bankless & Founder Earnifi
 🚁  Punk #5305

The entire lifecycle. I have to admit there's something from hooks I like... managing multiple contexts was a PITA when using classes. But other than that...

The amount of code duplication with classes was crazy. ‘onComponent*’ was hard to learn.

What did you find better about classes?

Does that mean you like it more with hooks? Hooks go against almost everything you learn when learning to code.

I hated react with classes so much I was using F# + Fable + Elmish to avoid it.

I disliked classes. Delved into FE after the introduction of hooks. I was mostly experiencing pain before. 😰