[aarpmcgee]

All I know is, the parts of my app that I implemented with state machines are by far the most stable, least buggy.

fwiw, if xstate feels like too much for whatever reason, https://thisrobot.life has seemed like a decent alternative to me.

[hashbig]

Same here, state machines are fantastic to extend state driven UIs without worrying about breaking existing behavior. If you find XState too verbose consider using a DSL that compiles down to JS like Lucy: https://lucylang.org

[astrange]

http://www.colm.net/open-source/ragel/ is good if you're more on the C side.

hmm… seaside… C side… has this been used for anything yet?

[simlevesque]

It seems like both of your links are projects from the same person, he must be passionated about state machines.

[psnehanshu]

Looks like Lucy compiles down to XState.

[cardamomo]

There's also a pared down, minimal version of xstate: https://github.com/statelyai/xstate/tree/main/packages/xstat...

[aarpmcgee]

I didn't know about this. Thanks a bunch.

[nailer]

You could also just make a very simple State machine. They don’t take a huge amount of code. you have a variable with the current state, you have a function that takes the previous state and the new State as arguments, now implement whatever logic you need. Not everything needs a library.

Pardon the unnecessary caps, I am using voice dictation.

[chombier]

When I need something lightweight I usually implement state machines using generators/coroutines when the language provides them, as they compose well and I find it easier to follow to control flow anyways.

[burntcaramel]

I’m curious how you use and compose generator functions?

I created a JavaScript state machine library using them to define each state. https://github.com/JavaScriptRegenerated/yieldmachine

I imagine your approach must be different?