asdf

I really appreciate the people who include descriptions and links for their list. My list has been pruned to avoid duplication (though perhaps knowing what's popular is a good metric too). asdf: https://github.com/asdf-vm/asdf - installs many different programming languages and supports installing different versions concurrently. I use it for go installs since distribution updates aren't usually fast enough. solaar: https://github.com/pwr/Solaar - handles configuring a logitech unifying receiver in Linux. Not really something you'd use multiple times, but am thankful it exists (also has a GUI too I believe).

Polyglots might also be interested in asdf (https://github.com/asdf-vm/asdf). It's like Pyenv but supports various languages via a plugin system (eg. https://github.com/danhper/asdf-python).

I've recently revisited asdf, and based on some testing, started moving my various compilers/interpreters to that. It's a "general" version manager - that works like rbenv for "all" languages. I'm not sure if I'd use it for deployment - but for development it's quite versatile. https://github.com/asdf-vm/asdf

Try a language manager. One I know to work on MacOS is asdf https://github.com/asdf-vm/asdf Then, there is something wrong with either brew or MacOS or both because we can install both Python 2 and 3 in parallel on any Linux with the system package manager.

I use asdf [0] for this. It lets you install and run different versions of any language. I keep a sensible global default if I'm just experimenting with stuff, but for any serious project I'd create a .tool-versions file in its root to specify the exact language version I'm developing and deploying against. [0] https://github.com/asdf-vm/asdf

I use asdf [0] for managing the multiple versions of different programming languages. Here's the golang [1] plugin. You need to be able to make some assumptions about your environment in order to implement tools like these. All you're doing is specifying the context in which certain commands within your workspace will run. A common pattern I've seen with some npm packages is to have the globally installed executable delegate to the project-specific version. This is a nice solution, but it's unrealistic to rewrite lots of projects to use this approach. IMO, text-based interfaces are still too limiting though. I want to interact with GUI apps programmatically as well! On macOS you can achieve a little bit of that with AppleScript (or with JavaScript in newer versions), but it's still not frictionless. [0] https://github.com/asdf-vm/asdf [1]

For Windows, I'd like to point to http://scoop.sh as mentioned here: https://news.ycombinator.com/item?id=17019197 It's a bit like a mix of (x)stow and apt for Windows. Or the good parts of arch aur with binary distribution. Should probably also mention that I'm experimenting with asdf as a version manager - to avoid a long list of setup in bashrc to adjust paths to various interpreters. It follows a lot of best practices that various dedicated version managers seem to pick up eventually: https://github.com/asdf-vm/asdf

I'm on 16.04 and I have no problems with that. I use the repositories of the developers, so I get the latest versions. I use Canonical's repositories for the OS and the software I don't really care much about. I had no problems with this approach (LibreOffice, PostgreSQL, etc). I occasionally run some software in a docker container to get the latest version, or to run multiple versions of the same server application (example: I've got two Redis for two different projects). Asdf [1] can manage multiple PostgreSQL versions (and several languages). The real advantage of staying on a LTS has been no big updates and no changes in the GUI. I'm on Gnome Flashback which I tweaked to be as closed as possible to Gnome 2. It seems that Gnome Shell eventually got enough extensions to also make it look like Gnome 2. I'll give it a try again after thos