Statecharts: hierarchical state machines

(statecharts.dev)

42 points | by sph 2 hours ago

2 comments

  • embedding-shape 8 minutes ago
    2 hours and not a single comment yet?! At one point, Statecharts seemed to be getting traction in the frontend/UI ecosystem, albeit tiny traction. Leveraging state machines (and particular Statecharts, which is basically compositions of state machines) for UI interactions makes complex flows so much easier to reason about! However, seems the traction eventually disappeared for unknown reasons, sadly.

    If this is the first time you're hearing about Statecharts, I highly recommend the book "Constructing the user interface with statecharts" by Ian Horrucks (https://archive.org/details/isbn_9780201342789/mode/2up) which yes, is from 1999, but probably the best introduction for how to actually apply and use Statecharts.

  • brandensilva 14 minutes ago
    I've always been a fan of state machines and have hoped for their adoption to grow.

    Having visual understanding of state is becoming increasingly important for AI generated code you don't nearly understand as well as the human variety.

    It seems many still favor store based reactivity state in frontend frameworks.

    I contribute to it being the default so why change and because libraries like xstate are far more difficult to learn the syntax and are more verbose. But with AI that's hardly an issue, so I wonder if there is more to it I don't see and we just haven't seen the state chart reach it's peak yet.