-
-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question] Comparison with mise #169
Comments
This might be worth my attention, we have one feedback #84 similar to this before. Maybe it will be supported later, depending on the amount of feedback.
Supporting Windows is the biggest advantage of As you said, Although we are all projects created to solve certain problems that At present, from a functional point of view, In general, if you're accustomed to unix-like systems and prefer a more established project, mise would be your optimal choice. |
Thank you for extended answer!
Fair enough, I didn't see that point, because I am just user, and not plugin developer 👍 |
As a Mise user, and former asdf user, I'd like to see it listed in the Readme. |
In fact, there is another similar tool, which is proto. You can simply create plugins through a Toml file, but if you want more complex functions, you'll have to write Rust code and compile it into wasm plugins. I like vfox largely because it is both simple and flexible to create or modify plugins using lua. |
There are many out there, no need to mention all of them :) |
You've added comparison with asdf, but there is another tool exists: mise (former
rtx
)Which takes same approach, as
vfox
, with environment variables, written in Rust, and supportsasdf
plugins out of the box.It also supports shims (as
asdf
), because environmental variables doesn't work well with IDEs.And overall looks much more mature, than
vfox
.One advantage I see in
vfox
is Windows support. Something else?The text was updated successfully, but these errors were encountered: