[mjs7231]

This feels like Trillian for virtualenvs. So typical that as engineers we keep abstracting everything we can until we run out of people that understand the basics. This tool looks like a great resource until step 4 when we create a virtualenv protocol. In chat clients, the protocols came first. For development IDEs adding auto-complete, it seems the protocol LSP came second. It's happening to language virtualenvs now as well.

1. You need a tool for X to solve an issue so you write it. (AIM)

2. Guy over there needs a tool for Y to solve the same issue, so he writes it. (Yahoo Chat)

3. So many tools exist, we need to merge them all into one. (Trillian, Adium)

4. Merging all the tools created a monster, we need a common protocol they all understand.

5. No one remembers how tool X works anymore, updates become more sparse.

6. Both X and Y are no longer popular, big company took over. (Slack)

[folkrav]

Not sure the comparison makes sense in this case. It doesn't have to do with virtualenvs. It's just a tool to install multiple interpreters/language runtimes in parallel and switch between them in an interactive shell with shims. In this case there are multiple tools that do the exact same for specific languages (pyenv/rbenv/goenv/...), this one does multiple runtimes, that's all. You'd still use your language's tooling for everything else.