> It was "To handle things with a lot of complicated changing state, try a state machine, and here's a simple example."
Right you are.
We should also acknowledge that state machines are a fundamental tool of GUI development. Either you use them, or you use them even though you're oblivious to them. There is no way around them.
Some GUI frameworks like Qt even develop and support their own state machine framework to drive their UIs.
Right you are.
We should also acknowledge that state machines are a fundamental tool of GUI development. Either you use them, or you use them even though you're oblivious to them. There is no way around them.
Some GUI frameworks like Qt even develop and support their own state machine framework to drive their UIs.
https://doc.qt.io/qt-5/statemachine-api.html
I mean, what do UI design people think a UI flow diagram is supposed to be?
Of all things to complain about React, state machines aren't one of them.