svelte-fsm VS BehaviorTree.CPP

svelte-fsm & svelte-tiny-virtual-list

https://github.com/kenkunz/svelte-fsm

Svelte + FSM turned one of the most convoluted UXes I've every dealt with into something manageable and almost pleasant.

This is a complex sales kiosk that must operate work limited or flapping network connectivity entire handling huge spikes in usage.

Svelte itself jusy gets out of the way, you don't fight it. The FSM makes your mental model explicit.

Something like "ok, we're halfway through the complex terminal registration process, the last network request timed out and there user pressed the back button, now what?"

With boolean flags its a mess.

Have a look at Behavior Trees, especially the BehaviorTreeCpp library https://www.behaviortree.dev The method is simple to understand, scales better than State Machines and if you implement the actions well they’re inherently modular. Nav2 uses them, and also BostonDynamics in their Spot SDK.

Unrelated to javascript, but in the robotics industry there is a trend towards Behaviour Trees. https://www.behaviortree.dev/ is a C++ library that was originally designed for controlling robots via ROS, but it appears to be decoupled from the ROS ecosystem so it could be used for other projects.

There is a basic UI available for editing the tree https://github.com/BehaviorTree/Groot