Comment

Comment on Tool to manage CLI tools

jeffhykin@lemm.ee ⁨11⁩ ⁨months⁩ ago

devbox
Tea from the creator of homebrew
it’s adsf but professional instead of crappy
And yes Nix (obligatory; BTW I use nix btw btw). Nix is supposed to be exactly what you’re asking for but it’s simply not ergonomic enough yet. I’ve been deep diving into it for 3 years and it’s still painful to setup a project with it. Devbox uses nix under the hood. It kinda of abuses nix and looses some of the guarantees but its usable/ergonomic.

Sort:hotnew top

savedbythezsh@sh.itjust.works ⁨11⁩ ⁨months⁩ ago
What’s your issue with asdf? It works really well for me

source
- jeffhykin@lemm.ee ⁨11⁩ ⁨months⁩ ago
  I don’t have anything against the author, but the tool doesn’t hold up under professional usage.
  
  The more versions you add, the slower it gets. And it can get really slow (that issue was opened in 2018, and it is fixable). And the delay is every time you call the command not every time you open a terminal or change directories.
  
  It’s janky
  
  It has [random side
  
  effects](github.com/asdf-vm/asdf/issues/693) that break cli tools
  
  (tools that are not even installed with ASDF) And the author said that’s a “wontfix”
  
  Pkgx, Devbox and nix avoid all these things.
  
  source
- Andy@programming.dev ⁨11⁩ ⁨months⁩ ago
  I’m not who you asked, and not a user of pkgx, but one of the reasons I prefer rtx (which supports asdf plugins) to asdf is that by default it doesn’t use shims, but updates the PATH instead.
  
  So for example, running which python will show me a clearly versioned python executable path, rather than a mysterious shim that represents a different realpath at different times.
  
  source