But I’m only implementing my machine in one language, why would this be useful? When do I need the same machine in multiple environments? Or are you referring to things like tooling for visualization etc?
As @CitizenKane pointed out, reusing statcharts between backend and frontend is a growingly popular use case.
Another benefit is you could use any visual tool (preferably web-based with collaborative capabilities so that all stackholders could work togehter) for state modeling to encapsulate business logics completely in statechart then export SCXML to any language you might be using.
It could be useful in a number of scenarios. For instance you may want to resolve state between a front-end and a back-end, so the ability to make transitions on both could be very useful.
Software engineer living on and off in Taipei for the past 20 years, if you like outdoor activities, especially road cycling, this is a mountain-climbers heaven, riding any direction for 30min will hit a gorgeous and cool mountain with spectacular views, on top of that most of the days including fall and winter it’s sunny and suitable for ride.
Drop me a line if you were ever here and longing for a joy ride ;)
It is indeed. However, I've found the problem of writing assignment actions correctly is very similar to the problem of managing ordinary variables without xstate. I'm wondering if I'm doing this right, since I thought xstate was supposed to make that kind of bug much rarer.
https://github.com/mikekelly/claude-sneakpeek
reply