Earlier quoted context omitted.
Because going back to non-packaged non-vetted flavor-of-the-month code is a retrograde step back to 1993. You lose consistency, you lose the ability to reliably recreate a same environment, you lose tested and low-friction security updates, you lose dependency management, you lose the security of a crypto web-of-trust, and you lose the google-fu of being on the exact same versions of software as thousands of other pe…
Your arguments sound nice in theory. Yet I don't know a single ruby shop who runs with a distro-packaged ruby, even though REE is available as a .deb.
Rbenv, an unobtrusive rvm replacement
41–50 of 115 posts
Re: Rbenv, an unobtrusive rvm replacement
#42Earlier quoted context omitted.
Apt-pinning and source packages are great ways to bring newer Ruby in to Debian stab The first thing I did after you left our common former employer was ditch all of the manually-installed REE on Ubuntu and changed to Debian stable with .debs of ruby and rubygems pinned in from testing. It was an improvement.
I'm not familiar with the technique you're referring to, is there a reference you could point me to that discusses "apt-pinning" packages from testing? We recently had a "there must be a better way" moment trying to get a standardized Ruby 1.9.2 installation set up - I think what you're describing is that better way.
Re: Rbenv, an unobtrusive rvm replacement
#43I got a simple solution for all you distro vs RVM people: People who prefer to use RVM - use RVM, people who prefer to use distro - use distro. Until you have proven that a server that runs distro is 2x more valuable in $ - post on HN and we could review it again. Reminding you of that we don't live in a totally symmetric universe.
Re: Rbenv, an unobtrusive rvm replacement
#44Earlier quoted context omitted.
Because going back to non-packaged non-vetted flavor-of-the-month code is a retrograde step back to 1993. You lose consistency, you lose the ability to reliably recreate a same environment, you lose tested and low-friction security updates, you lose dependency management, you lose the security of a crypto web-of-trust, and you lose the google-fu of being on the exact same versions of software as thousands of other pe…
Your arguments sound nice in theory. Yet I don't know a single ruby shop who runs with a distro-packaged ruby, even though REE is available as a .deb.
Re: Rbenv, an unobtrusive rvm replacement
#45Earlier quoted context omitted.
Because going back to non-packaged non-vetted flavor-of-the-month code is a retrograde step back to 1993. You lose consistency, you lose the ability to reliably recreate a same environment, you lose tested and low-friction security updates, you lose dependency management, you lose the security of a crypto web-of-trust, and you lose the google-fu of being on the exact same versions of software as thousands of other pe…
Your arguments sound nice in theory. Yet I don't know a single ruby shop who runs with a distro-packaged ruby, even though REE is available as a .deb.
Re: Rbenv, an unobtrusive rvm replacement
#46An official release with a web site and improved installation process should be out next week. If you're wondering "why would I use this instead of rvm?" be sure to read the readme: https://github.com/sstephenson/rbenv#readme
I've never liked how RVM overrides shell commands.
Re: Rbenv, an unobtrusive rvm replacement
#47Is it production ready? RVM is.
Re: Rbenv, an unobtrusive rvm replacement
#48Looks interesting. It's always been pretty amazing to me that a system like RVM remains so popular when it depends on overriding the operation of basic commands like 'cd'.
Re: Rbenv, an unobtrusive rvm replacement
#49An official release with a web site and improved installation process should be out next week. If you're wondering "why would I use this instead of rvm?" be sure to read the readme: https://github.com/sstephenson/rbenv#readme