Content pfp
Content
@
0 reply
0 recast
0 reaction

elboletaire 🗳️ pfp
elboletaire 🗳️
@elboletaire.eth
I see this and I raise it to the entire hooks system. React with classes was much better.
6 replies
0 recast
2 reactions

Grins pfp
Grins
@grins
constructor(props){ super(props); this.state = .... } Was so clunky though
1 reply
0 recast
0 reaction

elboletaire 🗳️ pfp
elboletaire 🗳️
@elboletaire.eth
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.
0 reply
0 recast
0 reaction