Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by wyuenho on Tuesday April 05, 2022 @11:51AM
(#30920533)
Exactly the reason to use direnv directly.
Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by rubyist5eva on Tuesday April 05, 2022 @12:37PM
(#30921192)
but then I still have to use some kind of package manager to manage multiple language runtime versions and brew/apt/dnf are all woefully inadequate
Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by wyuenho on Wednesday April 06, 2022 @09:19AM
(#30931626)
What's so inadequate? When you deploy, your CI/CD pipeline and production don't run on the apt/dnf versions of the language runtime?
Re:Switching from pyenv, rbenv, goenv and nvm to asdf
by rubyist5eva on Wednesday April 06, 2022 @06:06PM
(#30938055)
Our infrastructure runs on Ubuntu 20.04 across the board but, for example, our main Ruby on Rails monolith runs Ruby 3.0, but Canonical only packages 2.7 for Focal. We have a legacy service which runs on 2.5 and a few microservices that run on 2.7. Having language versions tied to specific OS versions was a massive PITA for us in the past, now it doesn't even really matter all the much what OS is running the code. If we just used apt versions we'd be stuck on Ubuntu 18.04 for ruby 2.5 and we'd have to ugprade the entire application in order to get it to run on 20.04 once it goes out of support. Yuck
Nevermind trying to setup a development environment where you have multiple dependencies on different language runtimes.
> asdf version resolution is slow which makes every command execution pay that penalty. asdf reshim is needed for finding new executables, and some tools are not happy with their executables being masked by shims.
> Perform asdf version resolution only once and defer environment loading to direnv.