huak VS mise

Curious question, since both are written in Rust (thus performance-wise both will be great) what other differences are there between rye and huak ?

and https://github.com/cnpryer/huak if it's stable will replace it for me :)

Hi! I'm working on https://github.com/cnpryer/huak. I really want to recreate what I enjoy about using Cargo but for the Python ecosystem.

Here’s an issue to track major feature status https://github.com/cnpryer/huak/issues/602

Thanks for the feedback! https://github.com/cnpryer/huak/pull/590

Yea I love that you found poetry and have enjoyed it so much. If you’re into package managers I’d really appreciate some of your feedback on Huak :). I just started it, but experiences like yours have given me the urge to build one.

I want you to tear me apart though so feel free to pick apart the architecture.md docs https://github.com/cnpryer/huak/blob/master/architecture.md

Why not just use a tool like asdf (https://asdf-vm.com/) or mise (https://mise.jdx.dev/)?

These tools have the advantage of not being multi-taskers and can manage version for all your tools. You wouldn’t need pyenv and npm and rvm and…

We’ve even started committing the .mise.toml files for projects to our repos. That way, since we work on multiple projects that may need multiple versions of the same tool, it’s handled and documented.

direnv + mise does exactly that. When I cd to various directories I get different env vars, it's pretty neat. Setting aliases would just be a case of adding them.

https://github.com/jdx/mise/discussions/1525 for an example of how I use direnv with mise.

https://mise.jdx.dev/direnv.html

https://mise.jdx.dev/templates.html

Installed bun js runtime (I used mise, btw)

Not nix based, but I really like https://github.com/jdx/mise too to manage dev tools.

It’s a modern version of https://github.com/asdf-vm/asdf written in Rust.

The purpose of a version manager is to help you navigate or install any tools for development easily. Version Manager can be one tool for each dependency (e.g. NVM, g) or One tool for all dependencies (e.g. asdf, mise).

I built mise-en-place[1] out of frustration trying to adopt nix. I found nix very challenging to adopt. I felt my system had a "split-brain" problem where it had a bunch of nix-built stuff that only worked with the other nix-built stuff and not the stuff that came from homebrew or whatever. Just a lot of binary-incompatibility problems I've never had to and certainly never wanted to deal with.

Now granted, I took a lot of code from other projects like asdf so I can't take full credit, but in my experience in the year having people use it pretty successfully, I think my "worse-is-better" approach actually is better than nix's for most people.

With mise, I don't deal with system libraries. If you want to install something that needs libyaml—well you need to install libyaml first. That seems like a downside but I think it's precisely _that_ which had made the project a success. With mise, I work _with_ your system—I don't try to bypass it like nix. Yes you might need to run apt or brew to get some dependencies up to date before you install something. mise is great at managing dev tools but it stays out of your system.

Is it reproducible? Heavens no. I don't think it should be. I think it should be easy to use and nix (nor nixos) will never be that. I _regularly_ help frustrated users attempting to use nixos because people online say it's great but they have no clue what shared objects are and why nothing they do ever seems to work like it does with Ubuntu.

Check my tool out if you haven't seen it yet. I just added support for other backends starting with npm and cargo—so no more `npm i -g` of tools into some bottomless pit of CLIs you'll never look at again.

[1]: https://github.com/jdx/mise