At first, I had thought what is its point, but this post made me wonder about the fact that I myself don't use sandboxes (even though I very much think that they are a good option and recommend it to other people!)

I tried to use smolvm[0] on macOS and although its really great but then it was still a bit of an hassle to install maki.sh and It wasn't an entirely smooth sailing process in the start and I can see why there is some initial friction to it.

So I am gonna try it out as well and I think that this might be damn effective at what its trying to solve (simplifying sandboxing to be the norm rather than the exception)

For example. Even within Smolvm, I had to install maki (debug the issues in installing that as there were some errors), setup my api key in that, install gh, login to gh to finally have a working sandbox that can have my environment and I imagine that moving files from VM to host and vice versa is a tad-bit complicated without compromising on security (I think that I just create a private github repo for this purpose if its a coding project, which also helps in actually cataloging all the projects for myself as well!)

and in some way, I think that this can act as the bridge course between sandboxing as well, I mean, I have finally introduced sandboxing on my local machine (although for sometimes, I just treat my vps machines as sandbox but nonetheless there are times when I just run maki on my local machine and I think that even with smolvm I might still have this), I definitely see the point of it.

I haven't really tried it yet as it made me go rather on the smolvm side of things but hopefully going to try out this

This seems like a project and I have starred the repo, good day!

[0]: https://github.com/smol-machines/smolvm