Live data from Hacker News

Asdf – An Extendable Version Manager

asdf-vm.com

91–100 of 100 posts

Re: Asdf – An Extendable Version Manager

#91
post #81
post #79

Earlier quoted context omitted.

Sure there is. One of the proposed successors to ASDF the Common Lisp package manager is XCVB ( https://common-lisp.net/project/xcvb/ ), the eXtensible Component Verifier and Builder.

Why is there no common place where people can see names that have been used already? It could make us avoid such nuissance.

There is. It's called Debian.

Re: Asdf – An Extendable Version Manager

#93
post #77

We use it at GitLab since a few months in order to manage our development toolchain [0]. Before we had people using rvm, rbenv, nvm, homebrew, system packages and everything in between. Supporting our engineers and non-engineers has been a lot easier since asdf, and the whole version manager related issues calmed down a bit. The only thing I miss from homebrew is the pre-compiled stuff like e.g. Postgres or redis [0]…

Have you used or considered nix before? I’m looking into both right now and wonder what the advantage of asdf is, as nix seems to be the more robust option.

Re: Asdf – An Extendable Version Manager

#94

"Please head over the documentation site" is a link back to the site. The ballad links to an old repo (fortunately Github redirects it) The all-plugins page 404's. After giving up on the website I look at the code. It's a shell script. Wonderful. I'll stick with Nix any day. Or maybe conda.

I wanted to see what the differences between asdf and nix were, and found a pretty lengthy article[1] that explained it quite well in the first few paragraphs. asdf is better than nothing, and better than multiple version managers for each language in one project, but it is a far cry from the portability and reliability of nix.

If you wanna do something quickly to ease the pain of version management, asdf is there, helpful, and ergonomic. But if you want to make version management an issue of the past and fix it for good, nix is the way to go.

So they both have their use. nix just feels more proper.

Re: Asdf – An Extendable Version Manager

#95

"Please head over the documentation site" is a link back to the site. The ballad links to an old repo (fortunately Github redirects it) The all-plugins page 404's. After giving up on the website I look at the code. It's a shell script. Wonderful. I'll stick with Nix any day. Or maybe conda.

I wanted to see what the differences between asdf and nix were, and found a pretty lengthy article[1] that explained it quite well in the first few paragraphs. asdf is better than nothing, and better than multiple version managers for each language in one project, but it is a far cry from the portability and reliability of nix. If you wanna do something quickly to ease the pain of version management, asdf is there, h…

I'd be interested in that article - be great if you could re-up the footnote :)

Re: Asdf – An Extendable Version Manager

#96
post #77

We use it at GitLab since a few months in order to manage our development toolchain [0]. Before we had people using rvm, rbenv, nvm, homebrew, system packages and everything in between. Supporting our engineers and non-engineers has been a lot easier since asdf, and the whole version manager related issues calmed down a bit. The only thing I miss from homebrew is the pre-compiled stuff like e.g. Postgres or redis [0]…

Have you used or considered nix before? I’m looking into both right now and wonder what the advantage of asdf is, as nix seems to be the more robust option.

I think we have looked into Nix briefly. It seems great. I wonder how well it works cross-platform or if it forces us to either maintain a Darwin and Linux version, or using the Linux version in a VM.

Re: Asdf – An Extendable Version Manager

#97

Earlier quoted context omitted.

I wanted to see what the differences between asdf and nix were, and found a pretty lengthy article[1] that explained it quite well in the first few paragraphs. asdf is better than nothing, and better than multiple version managers for each language in one project, but it is a far cry from the portability and reliability of nix. If you wanna do something quickly to ease the pain of version management, asdf is there, h…

I'd be interested in that article - be great if you could re-up the footnote :)

Oh damnit, completely forgot. Seems like I can’t edit my comment anymore, so here you go: https://ejpcmac.net/blog/about-using-nix-in-my-development-w...

Re: Asdf – An Extendable Version Manager

#98
post #96

Earlier quoted context omitted.

Have you used or considered nix before? I’m looking into both right now and wonder what the advantage of asdf is, as nix seems to be the more robust option.

I think we have looked into Nix briefly. It seems great. I wonder how well it works cross-platform or if it forces us to either maintain a Darwin and Linux version, or using the Linux version in a VM.

The whole idea seems to be that you don’t need to care about the platform. You use the same .nix file to start a shell with a custom environment on Linux, Darwin and Windows WSL. Even aarch64 is fully supported and all binary packages are built for it as well, so even on the M1 Macs it should just work.

Granted, I didn’t try any of this yet, but the more I read about it, the more I want to. You can even build docker images from the .nix file so the CI/CD pipeline will have the exact same environment as all the dev machines.

Re: Asdf – An Extendable Version Manager

#100
post #81
post #79

Earlier quoted context omitted.

Sure there is. One of the proposed successors to ASDF the Common Lisp package manager is XCVB ( https://common-lisp.net/project/xcvb/ ), the eXtensible Component Verifier and Builder.

Why is there no common place where people can see names that have been used already? It could make us avoid such nuissance.

There is, google: "asdf programming". All the other projects named asdf pop up. The people who do not use google will not use a new common place either.
Post reply on HN