#Is the project going in a closed-source direction?

1 messages · Page 1 of 1 (latest)

solar forum
#

Hi, I'm using XState as part of a front-end application, and recently found out that the old "xstate-viz" was archived in favor of a new, apparently closed-source visualizer.
The xstate-inspect package also seems to have buried the URL for this inspector on the code, so it's less obvious how to use another option.

Due to privacy concerns, I can't use the online visualizer, and being forced to login makes it even worse.
Xstate-viz could be run locally to inspect the machine, which now seems no longer possible, and this is very bad for our workflow.

I also fear for the future of the VSCode extension visualizer, which is essential. Is it also going to be closed and charged? If not, can I use it to inspect a running machine?

Overall, is this project becoming a closed-source subscription-based SaaS? I'd like to know the extension of these changes so I can make the best decision on my project.

balmy glacier
#

Hey, appreciate your concerns. Will answer them one-by-one:

#

The new @statelyai/inspect package is completely open-source, MIT-licensed. It basically acts as a protocol for communicating state/actor changes to a visual inspector, such as (but not limited to) the Stately Inspector

#

Stately Inspector does not require login. It is closed-source, but it can be used freely.

#

We are working on the next version of the VS Code extension to support XState v5 and more features. The same state machine editing that you could do in the current extension will be available all the same in the updated extension. There are new features that will require logging in, but for the most part, the workflow should be the same.

#

Privacy is a valid concern. You can view our privacy policy here: https://stately.ai/privacy

Privacy | Stately

The Stately privacy policy outlines how we collect, use, and protect your personal data when you use our platform.

#

The core parts of XState will always be free and open-source, MIT-licensed. Any developer can build 3rd-party inspectors/editors/visualizers on top of XState, and we encourage it!

At the same time, we need to make money somehow to continue supporting the open-source project and building great tooling for developers. It's a tricky problem to solve, but we're figuring out the best balance.

solar forum
#

Thank you for the quick answer.
I couldn't find a way into the Stately Studio without logging in, which is kind of bad for presenting the xstate basics for new people - it's no longer an awesome tool for which companies can pay for training, it's a monthly paid service which goes at the center of a software solution. My personal grievance with your decision is how it undermines the beauty of xstate over other state machine libs, which was offering a full environment for the developer, in favor of a pretty aggressive tracking+subscription policy.
I get you need to make money, the open source struggle is tangible for me, I'm just grieving the loss of a very nice tool.

Apart from that, I believe my questions were answered. Unfortunately due to the closed-source extension and editor and the policy terms, I'll probably need to move on, which I find more sad than anything.

Once again, thanks for the support and I truly hope all the best for you and your team, XState is an awesome tool, I just needed to share this. I think we can close this topic now

balmy glacier
#

But also, signing up and logging in takes very little effort and the Studio can be used for free. I don't plan on ever taking away the free tier. I feel that registering for free is the least that someone can do in return for a tool that we have spent years working days, nights, and weekends on.