Live data from Hacker News

Asdf – An Extendable Version Manager

asdf-vm.com

81–90 of 100 posts

Re: Asdf – An Extendable Version Manager

#81
post #79

Earlier quoted context omitted.

Yeah I'm not usually a "hey there's another project with that name" kinda guy but, build manager and version manager? Isn't there some other part of the keyboard they could have mashed?

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.

Re: Asdf – An Extendable Version Manager

#83
I introduced ASDF at the company I currently work at and it spread like wildfire to every team.

Having a single version manager that manages the versions for numerous tools across different teams has been invaluable.

Re: Asdf – An Extendable Version Manager

#84

"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.

Yes. My experience with nix-shell[0] is very smooth so far.

[0] https://nixos.wiki/wiki/Development_environment_with_nix-she...

Re: Asdf – An Extendable Version Manager

#86
ASDF is great. I've been using it for four years now with no real complaints.

It's made collaboration with contractors much easier to just be able to drop a .tool-versions file into a project and know that regardless of what OS each of us are on, we'll have the same language versions.

Re: Asdf – An Extendable Version Manager

#88
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]…

For Postgres & Redis version management, have you seen DBngin? It supports MySQL, too.

https://github.com/TablePlus/DBngin

Re: Asdf – An Extendable Version Manager

#89
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]…

For Postgres & Redis version management, have you seen DBngin? It supports MySQL, too. https://github.com/TablePlus/DBngin

Looks nice, but we’d still need to support Linux too. And CLI for the win!

Eventually moving our Postgres, Redis, etc. to docker is also a solution. Unfortunately node and ruby take a performance hit if you mount them into containers and update loads of files.

Re: Asdf – An Extendable Version Manager

#90
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.

Why don't you build one? The worst that can happen is that you learn the answer to your question.
Post reply on HN