Disagree. Hooks took one problem and reshaped it, they didn’t actually solve the problem.

With hooks you still need to think about lifecycle, side effects, and state, but the syntax changes.

The real solution is overall application design and thinking through architecture, but unfortunately that’s higher effort than “just use hooks bro”.

Agreed. Thinking about lifecycle, side effects and state doesn’t just go away. It’s inherent to the system you are building. Hooks is a way to address that, class lifecycle methods are another. None of these tools will magically let you ignore proper design.

Agreed but hooks did solve composability. It’s easier to implement very complex handling, like drag and drop interactions.