4 ms·
For a good while I thought I was the only one who is against hooks. It's good to see there are two of us. By the looks of the other comments here, maybe even th
by oaxacaoaxaca 5y ago
For a good while I thought I was the only one who is against hooks. It's good to see there are two of us. By the looks of the other comments here, maybe even three.
- reactspa 5y agoHooks never grew on me. I pretty much stopped paying attention to new versions after React 14. KISS - keep it stupid simple. I suspect that some Devs new to JS didn't like the various definitions of "this", and Hooks was supposed to help them out.
- azangru 5y ago> I suspect that some Devs new to JS didn't like the various definitions of "this", and Hooks was supposed to help them out. No, stale closures caused by hooks are more confusing than what "this" has ever been, especially since this-related problems are mitigated with fat arrows and class property assignment. No, as far as I understand, the driving force behind the hooks was the vision of the coming concurrent mode, for which class components posed some difficult problems somehow.
- lhorie 5y agoThere are a number of people that dislike hooks, many of who are vocal in React threads. Basically the entire classes-are-fine camp do, and there are a few of us in the "the React team doesn't appear to understand the functional paradigm" camp. I fully expect that in a few years React will be widely seen as a J2EE-like poster child of over-engineering shark jumping for the functional paradigm. I already do.