Show HN: Browser based state machine simulator and visualizer
svylabs.github.io
Show HN: Browser based state machine simulator and visualizer
1–10 of 11 posts
Re: Show HN: Browser based state machine simulator and visualizer
#2Re: Show HN: Browser based state machine simulator and visualizer
#3Re: Show HN: Browser based state machine simulator and visualizer
#4This is cool too! I love state machines.
Re: Show HN: Browser based state machine simulator and visualizer
#5Re: Show HN: Browser based state machine simulator and visualizer
#6The configuration reminds me a lot of XState, which has a beautiful visualizer/simulator (with a new version on the way I think): https://stately.ai/viz This is cool too! I love state machines.
Yes, it looks similar to XState. When I built it, I didn't know of XState, but of course, I did use a lot of AI to create this, so the configuration is similar to XState.
But my plan is to see if there is opportunity with this elsewhere, orthogonal to what stately seems to be doing.
Re: Show HN: Browser based state machine simulator and visualizer
#7You meant this perhaps? https://svylabs.github.io/smacthat/
Re: Show HN: Browser based state machine simulator and visualizer
#8I get a 404 immediately
Re: Show HN: Browser based state machine simulator and visualizer
#9Really cool! Love the XState-inspired API ;-)
Actually I didn't know of XState when I built this, I had built this for my own workflow.
I did use AI to build this, so credits to AI for coming up with the right model, inspired by XState.
My plan is to build a slightly orthogonal version of what stately / xstate offers, even though right now it looks similar.
You can check out eigenarc.com for how I'm thinking of this.
Re: Show HN: Browser based state machine simulator and visualizer
#10The configuration reminds me a lot of XState, which has a beautiful visualizer/simulator (with a new version on the way I think): https://stately.ai/viz This is cool too! I love state machines.
Thanks for checking out. Yes, it looks similar to XState. When I built it, I didn't know of XState, but of course, I did use a lot of AI to create this, so the configuration is similar to XState. But my plan is to see if there is opportunity with this elsewhere, orthogonal to what stately seems to be doing.
In my opinion this is a good thing. It's a really well-designed API. It's easily my favourite approach to defining state machines that I've encountered across several languages.
> see if there is opportunity with this elsewhere
Any plans to share yet? This sounds interesting!