Skip to content
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

Open
victordidenko opened this issue Apr 2, 2024 · 5 comments
Open

[Question] Comparison with mise #169

victordidenko opened this issue Apr 2, 2024 · 5 comments
Labels
question Further information is requested

Comments

@victordidenko
Copy link

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 supports asdf 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?

@victordidenko victordidenko added the question Further information is requested label Apr 2, 2024
@aooohan
Copy link
Member

aooohan commented Apr 3, 2024

It also supports shims (as asdf), because environmental variables doesn't work well with IDEs.

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.

One advantage I see in vfox is Windows support. Something else?

Supporting Windows is the biggest advantage of vfox for now.

As you said, mise is indeed more mature than vfox. As a four-month-old project, vfox still has many areas that need to be optimized. For example, the plug-in ecology, mise benefits from the original plug-in ecology of asdf. And vfox We need to re-establish it. It can be seen that the directions of vfox and mise are not consistent at all.

Although we are all projects created to solve certain problems that asdf itself cannot solve, but vfox for asdf performance issues, cumbersome shell plugin development issues and Windows support issues. And mise only solves the performance and UX of asdf.

At present, from a functional point of view, vfox does not have any better advantages than mise for now, because vfox is simple enough and new.

In general, if you're accustomed to unix-like systems and prefer a more established project, mise would be your optimal choice.

@victordidenko
Copy link
Author

Thank you for extended answer!

cumbersome shell plugin development issues

Fair enough, I didn't see that point, because I am just user, and not plugin developer 👍

@megatux
Copy link

megatux commented Apr 22, 2024

As a Mise user, and former asdf user, I'd like to see it listed in the Readme.
I'll definitely try vfox! looks great and I love the choice of Lua for its plugins.
Thanks a lot!

@aooohan aooohan pinned this issue Apr 23, 2024
@yanecc
Copy link
Contributor

yanecc commented Apr 23, 2024

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.

@victordidenko
Copy link
Author

There are many out there, no need to mention all of them :)
I've created this issue because vfox deliberately compares itself to a asdf and consider itself as its competitor.
proto as I see, on the other hand, as part of a bigger toolchain, has different targets.
It would be interesting to see comparisons with many other version managers, true, but I was ment to ask just about mise, because it already solves asdf issues, which vfox claims to be solving as well.

@aooohan aooohan unpinned this issue Apr 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

4 participants