4 ms·
Robot, in turn, links to [0], which has a nice section that goes over an example of when all this is useful (which was missing from the Lucy page). [0]: https:
by CGamesPlay 2y ago
Robot, in turn, links to [0], which has a nice section that goes over an example of when all this is useful (which was missing from the Lucy page).
[0]: https://thisrobot.life https://thisrobot.life
- whilenot-dev 2y agoAnd the following part Instead of conforming to an XML specification created decades ago, Robot takes the best ideas from both academia and real-world usage of finite state machines. This makes state machines easy to read and understand, as there is only one way to do most common tasks. ...is hinting at some disagreements with XState's approach. Would be nice to have a visualization tool, like the kind XState has, for any FSM library (like robot) though.
- steve_adams_86 2y agoThe visualization tool goes a long way in helping non-developers understand what logic is actually doing, from a relatively wide perspective. It’s valuable for sure
- codethief 2y agoWhere do you see the disagreement with XState's approach?
- whilenot-dev 2y agoXState famously always conformed to the SCXML spec[0]. It isn't mentioned anymore in the current version anywhere(?), but you can still see it in the v4 docs[1]. [0]: https://www.w3.org/TR/scxml/ https://www.w3.org/TR/scxml/ [1]: https://stately.ai/docs/xstate-v4/xstate/advanced/scxml https://stately.ai/docs/xstate-v4/xstate/advanced/scxml
- codethief 2y agoThanks!
- codethief 2y agoI'm on my phone right now, so can't try Robot but I'm wondering what the type safety story looks like. For instance, in the example in "Getting started" the variable `users` is defined irrespective of the state, even though it is only available in the `loaded` state.