aooohan

> I just unpack node to different folders and set PATH. Why would I need any tool for that?

To put it simply, vfox will help you do this. Unzip node, golang, etc. to $HOME/.version-fox/cache. When you write `vfox use [email protected]`, it will automatically configure PATH for you. Free your hands, you don't need to think about where to download nodejs, golang, etc. runtime, nor how to configure PATH. Especially on Windows, configuring PATH is still quite troublesome.

Yes! Compared to asdf, vfox has made some UX improvements to make the commands more concise.

I've used all of these tools in conjunction with my own usage habits, which is why I'm developing vfox from scratch rather than based on asdf. so the issue at hand for vfox is the need to rebuild the plugin ecology. There's no way to utilise off-the-shelf asdf plugins.

But it does nothing for Windows.

No, these are two completely different tools.

Compared to Cygwin, vfox is just a small tool which is more like scoop.

Simply put, while scoop can only install the latest version, vfox can install any version, and has some extra features for project development, such as using different versions for different projects, automatic switching between versions, and so on.

Honestly, the python plugin is a bit problematic on Windows at the moment, the next plugin version should fix that.

But on unix it is also built using python-build. For me, a light python user, there is no difference between using vfox and using pyenv.

Thanks for the recommendation！;)