Thread by @championswimmer

Understanding state management is definitely like the final boss of the frontend framework game. It is sometimes to hard to wrap your head around, but it need not be.

In Flutter world, I blame BloC to be have made the thing very convoluted for beginners to understand.

Step 1 of understanding state should be to separate state from UI.

Many over-powered state management frameworks have mechanisms of _constructing UI from state_, which is useful for seasoned devs, but hinders beginners from learning what happens under the hood

Frameworks like Vue or Flutter which have internal mechanism of state inside their components/widgets (i.e. the UI primitives), also has a downside. People start off thinking state as a part of UI primitives, which it isn't at all.

Best if your UI primitives have no mechanism of carrying state, that way, beginners learn to manage the UI tree and the state separately from each other.

Most tutorials consider beginners too naive to be told about state management to in the beginning, and beat around the bush, thus leading them into storing state inside UI tree.

And then people write blogs and wax eloquent about learning to "life state up".

Today I see the whole herd of junior Android developers running into Jetpack Compose (which is just Flutter rewritten in Kotlin), and entangling themselves into callback hells for the same reason.

The older folks then tell them "ah you need to learn to life the state up".

None of this would happen if people are simple taught to deal with state and UI tree separate from each other.

Do not guard beginners from the perils of state management by not teaching them about it early on.

Heck, send them to stately.ai/viz before teaching UI.