4 ms·
I recently discovered state charts via xstate in JS/React. A truly empowering experience. I was able to resolve spaghetti code that accounted for 75% of busines
by dmitryminkovsky 6y ago
I recently discovered state charts via xstate in JS/React. A truly empowering experience. I was able to resolve spaghetti code that accounted for 75% of business logic (not all bad paths handled, or good ones either really) and “worked” 90% of the time (certain transitions in certain states not implemented) into a state machine that accounts for all cases and actually works. Without the state machine, complexity seemed to scale exponentially. With the state machine, complexity scales linearly.
Since then I’ve thought I’m not sure how I could adopt a UI system without a state charts implementation. Most user interactions aren’t that complicated, but some can be, and really do need to be resolved into state machines unless you are an expert spaghetti developer.
So, very glad to see this and hope to see more and more implementations.
- davidkpiano 6y agoCompletely agree with you, and thanks for the kind words about XState! (I'm the creator)
- dmitryminkovsky 6y agoThanks a lot for XState. As empowering a tool for reactivestate management as react is for reactive UI rendering.
- CitizenKane 6y agoWanted to add some more kind words about XState. It's a key component of a project I'm working on now with some pretty atypical requirements relative to most web projects. It's been a lifesaver in that regard, and I think we would be a bit sunk without it.
- cryo 6y agoThank you very much for working on XState, it's a real game changer. Always enjoy your Twitter posts about state machines. Keep up the good work, just realised XState has a Github sponsor button, count me in soon.