You know, with how hooks work in Vue, things seem be easier to understand and get started with.

Though at least with React I've had plenty of projects end up with render loops that are hard to debug because of how everything is written. So much so, that I wrote a blog post about it a while back "Modern React is broken": https://blog.kronis.dev/everything%20is%20broken/modern-reac...

Personally I wish that we could already have some tooling that'd tell you something along the lines of:

  Render loop detected! The following chain of calls was responsible for it: A -> B -> C -> A -> B -> ...
  Please check the useEffect hook on line X, which has the following items in its dependency array which changed: [Y, Z]

And lifecycle methods are just as "magical" as hooks. If you just thought about why the "rules of hooks" exist for a moment instead of just hating change for the sake of it existing, you could probably intuit how they work under the hood.

Lastly, lifecycle methods don't allow you to co-locate feature-related code, can actually create more bugs (if you have logic in `componentDidMount` but forget to add something similar to `componentDidUpdate` for example), and any logic contained within lifecycle methods isn't composable / reusable.

I really don't understand where you're coming from at all with this.