I had similar thoughts but was so glad I stuck with season 4, it is probably one of the best seasons of TV I've ever seen and provided satisfactory closure. IMO season 4 is worth watching no matter what you thought of the middle seasons, I've rewatched it a few times which I almost never do.

I felt the same way. It sort of fell apart during the later seasons. But the final season, especially the second half of it is easily one of my favorite seasons ever. The writing is absolutely incredible, especially as a software developer. Basically like an opposite lost, everything comes together in an incredibly satisfying way.

The project started out as a movie and so it is no surprise it had a great start and end but got a little lost in the middle when the idea needed to be stretched out.

You should continue watching, it all comes together in the last half of the 4th season. You'll understand why Elliot is the way he is.

You are sorely missing out. Mr. Robot is laid out in three acts. You cannot skip the last season (Act III), it provides closure and ties the seeming chaos of the middle two seasons (collectively, Act II) into a cohesive plot.

When I read about season 5, I didn’t interpret it to mean that the entire show was planned out, just that the ending was.

I've seen people cause all kinds of problems with hooks, but I don't believe I've ever seen deadlock. Can you elaborate?

Can you elaborate on the deadlock risk, or link to further reading?

Haile's work seems mostly to be stream-based like RXJS, is that right? They seem to be reactive components. Can you show me how I can compose pieces of life cycles together using Haile's libraries like I can with hooks?

Maybe. I'm not sure who's really hyping up ancient texts like the Bible these days, or some of the other answers as well.

It seems you are. I'd encourage you to read briefly through [1] that I linked above, it shows why hooks are needed rather than just functions. Basically you're passing state around in a Closure such that you can hook into life cycles from any part of the app. This means that I can create a self contained hook for something like making an animation for a component and making it usable for any component I want, rather than wrapping everything into an AnimationComponent just to get the lifecycle state. I can reuse this behavior anywhere else in the app.

I think the point is you don't have to deal with anything else. You only have to set state!