Frustrations with React Hooks

Post by bcheung » Wed, Sep 11, 2019, 4:38 AM UTC

shantly wrote: post #37

bcheung wrote: post #30

Overall I think React hooks are an improvement. My codebase is usually shorter and there is a lot less typing involved. But hooks creates abstractions the developer needs to deal with that never existed before. Hooks are not functional because they break referential transparency of functions. You have to track dependencies manually and hooks are more difficult than they need to be for the "componentDidMount" equivale…

> The positional order seems like it would be easy to work around if they allowed you to pass in a key. Not sure why that isn't available. IIRC it's because they implemented their own method lookup table (!) to associate with the Component object (!) but as a FIFO queue, more or less. I assume either for ideological (that's how they wanted it to work) reasons or because they (probably correctly) reasoned that loading…

Post by filleduchaos » Wed, Sep 11, 2019, 11:17 AM UTC

Unbeliever69 wrote: post #93

nooyurrsdey wrote: post #62

What's lost in all this is that classes are simple and understandable. Introducing all these new paradigms removes that simplicity. Everyone is ready to hate on classes but they have been robust structures for a long time

I think that what is lost is that Javascript is more of a functional language than an object-oriented one and a move to hooks embraces its functional roots while eliminating numerous footguns (this), simplifying reuse, and reducing redundancy.

Post by Normal_gaussian » Wed, Sep 11, 2019, 11:58 AM UTC

bcheung wrote: post #130

Normal_gaussian wrote: post #36

Earlier quoted context omitted.

You absolutely can create abstractions where a hook calls another hook. It is perhaps the single most useful change hooks have given me. Of course you need to follow the same rules in the hook (always call every hook it calls, in the same order, so you don't mess up the order above).

Not inside of useEffect.

Post by cercatrova » Thu, Sep 12, 2019, 6:10 AM UTC

ssalka wrote: post #107

aidos wrote: post #87

Earlier quoted context omitted.

Nothing stops you from using pure function components, and you should where possible. But eventually, you need to hold state somewhere. You don't need to put it in your components, but you do need to deal with it. If anything, hooks are a nice middle ground where the behaviour becomes declarative.

My personal opinion is that state should be contained in some sort of class or data structure, separate from functional architectures where the notion of state is generally avoided. So my usual suggestion would be to use either a class component (or redux or insert favorite state mgmt solution here ) for your state, and then inject the state as props to your function components

Post by cdeutsch » Tue, Sep 17, 2019, 10:11 PM UTC

peternicky wrote: post #34

Not to sound like a jerk but I cannot help but think this dude is whining about very petty issues. I read the article and found it to contain very weak arguments. I totally can relate to the frustration when learning new stuff, especially when you have done things one way for years. Personally, the first month or so that I used hooks in react, it wasn’t pleasant, mostly due to me being uncomfortable with the addition…