4 ms·

Yep. Moved from `rvm` to `rbenv` when it came out, but didn't realize how much magic it still did. Switched to `chruby` when it came out, was much nicer experie

Yep. Moved from `rvm` to `rbenv` when it came out, but didn't realize how much magic it still did. Switched to `chruby` when it came out, was much nicer experience overall, and faster too. Just wish the Emacs package for chruby was written a little less ad-hoc.

hvis 11y ago
rbenv doesn't require _any_ special integration to be used from inside Emacs. As long as chruby needs that, it doesn't seem like a good alternative to me.
- regularfry 11y ago
  Chruby's so small that you might as well rewrite it in elisp.
cheapsteak 11y ago
As a ruby outsider, I wonder do those have any practical effects on how you write/run programs? Do they save time or prevent bugs? Why is versioning such a huge problem in ruby?
- integraton 11y ago
  They are tools for managing multiple installed versions of a programming language. When developing software, we often specify dependencies using version numbers, which indicate the version of the language or library that should be used when running the software. Running the software with the specified language runtime or library version ensures that the expected features of that library or language runtime are available and also helps avoid unexpected issues related to differences in the environments, including different developer's local systems as well as remote server environments. In the case of a programming language runtime, if you have one project that's configured to use version 2.2.4 of a language and another that's configured to use version 2.1.0, these tools provide an easy way to install and switch between the two versions. This is not unique to Ruby, and similar projects exist for other languages. For example, nvm (https://github.com/creationix/nvm https://github.com/creationix/nvm) and n (https://github.com/tj/n https://github.com/tj/n) provide something similar for Node (JavaScript), gvm (https://github.com/moovweb/gvm https://github.com/moovweb/gvm) for Go, and multirust (https://github.com/brson/multirust https://github.com/brson/multirust) for Rust.
  - mfisher87 11y ago
    I've dabbled a little bit in Ruby, and I found this to be a much larger problem than it is with Python. Most systems have python 2 and/or python 3. Beyond that, I've rarely need to worry very much about which Python version I have. But for every new Ruby application I install on my machine, I'm messing around with rvm. Is it truly a difference between the languages release strategy or is this just my perception because of limited experience with Ruby? I found it to be a huge pain in the ass.
    - lars512 11y ago
      It's annoying for sure, and I like that we don't need it in Python land. But, in situations when we do want to target multiple Python versions, an identical approach using pyenv works well. I've come to appreciate it more.
    - deleted 11y ago
      [deleted]
    - lyime 11y ago
      It's not really a problem per say. It's just taste really. There are multiple good options for managing ruby versions and environments. (as well as other languages like Phython, see pyenv). I don't necessarily switch to ruby versions between projects or with frequency. That being said, ruby is in active development and with new versions there are many improvements to performance and security. So developers like to try the latest and test out their apps, libraries and frameworks.
  - cheapsteak 11y ago
    I'm sorry I wasn't more clear, I'm wondering why there seems to be a war of sorts between which version manager to use for ruby. Are the differences between rvm, rbenv, chruby, ruby-install practical or purely ideological? There doesn't seem to be this kind of disagreement over which version manager is best in other languages, just ruby, why is that?
    - whistlerbrk 11y ago
- briandear 11y ago
  Libraries that work for an older version of ruby won't always be forward compatible. So if you're working in many projects you can't simply use the latest version of ruby. Then you have things like Jruby which is incompatible with some of the libraries designed for MRI. So, being able to segregate rubies is essential.
NatW 11y ago
I've been perfectly content using RVM https://rvm.io/ https://rvm.io/ - with all the functionality I need, and reliability, too. What am I missing out on?
- elliotec 11y ago
  Rbenv is much smaller and only does ruby version changes and installations with the ruby install add on. rvm is bigger and has more features but is a bigger pain to use in my experience.
  - lucaspiller 11y ago
    Also the whole Gemset thing is basically redundant now Bundler has become the standard way of locking dependencies (Gems).
- technion 11y ago
  I fell on rvm because it seems to be the "default" recommendation. I don't see a need to use something "better" if the raw tool does the job perfectly. I do get annoyed that "rvm list known" tends to only show old versions. For example, it suggests it can install ruby-2.2.1, but I'm fully aware 2.2.4 is available, as is ruby 2.3 now. And for me at least, this problem is consistent after applying the standard advice of "get the latest rvm".
  - aaronbrethorst 11y ago
    rvm was perfectly happy to install Ruby 2.3.0 for me this morning, upgrading me from 2.2.4, which is what I was using until last night.
  - mwpmaybe 11y ago
    rvm "stable" hasn't been updated in quite a while, last time I checked. you need to install the "dev" version.
- regularfry 11y ago
  The problem with rvm was always that it tried to do too much. With a tool like that, as long as it's working, you won't see the downside. When it breaks, it breaks in complicated, hard-to-debug ways. If you're saying it's reliable for you, that's great. That wasn't my experience.

hvis 11y ago

rbenv doesn't require _any_ special integration to be used from inside Emacs. As long as chruby needs that, it doesn't seem like a good alternative to me.

regularfry 11y ago
Chruby's so small that you might as well rewrite it in elisp.

cheapsteak 11y ago

As a ruby outsider, I wonder do those have any practical effects on how you write/run programs? Do they save time or prevent bugs? Why is versioning such a huge problem in ruby?

integraton 11y ago
They are tools for managing multiple installed versions of a programming language. When developing software, we often specify dependencies using version numbers, which indicate the version of the language or library that should be used when running the software. Running the software with the specified language runtime or library version ensures that the expected features of that library or language runtime are available and also helps avoid unexpected issues related to differences in the environments, including different developer's local systems as well as remote server environments. In the case of a programming language runtime, if you have one project that's configured to use version 2.2.4 of a language and another that's configured to use version 2.1.0, these tools provide an easy way to install and switch between the two versions. This is not unique to Ruby, and similar projects exist for other languages. For example, nvm (https://github.com/creationix/nvm https://github.com/creationix/nvm) and n (https://github.com/tj/n https://github.com/tj/n) provide something similar for Node (JavaScript), gvm (https://github.com/moovweb/gvm https://github.com/moovweb/gvm) for Go, and multirust (https://github.com/brson/multirust https://github.com/brson/multirust) for Rust.
- mfisher87 11y ago
  I've dabbled a little bit in Ruby, and I found this to be a much larger problem than it is with Python. Most systems have python 2 and/or python 3. Beyond that, I've rarely need to worry very much about which Python version I have. But for every new Ruby application I install on my machine, I'm messing around with rvm. Is it truly a difference between the languages release strategy or is this just my perception because of limited experience with Ruby? I found it to be a huge pain in the ass.
  - lars512 11y ago
    It's annoying for sure, and I like that we don't need it in Python land. But, in situations when we do want to target multiple Python versions, an identical approach using pyenv works well. I've come to appreciate it more.
  - deleted 11y ago
    [deleted]
  - lyime 11y ago
    It's not really a problem per say. It's just taste really. There are multiple good options for managing ruby versions and environments. (as well as other languages like Phython, see pyenv). I don't necessarily switch to ruby versions between projects or with frequency. That being said, ruby is in active development and with new versions there are many improvements to performance and security. So developers like to try the latest and test out their apps, libraries and frameworks.
- cheapsteak 11y ago
  I'm sorry I wasn't more clear, I'm wondering why there seems to be a war of sorts between which version manager to use for ruby. Are the differences between rvm, rbenv, chruby, ruby-install practical or purely ideological? There doesn't seem to be this kind of disagreement over which version manager is best in other languages, just ruby, why is that?
  - whistlerbrk 11y ago
briandear 11y ago
Libraries that work for an older version of ruby won't always be forward compatible. So if you're working in many projects you can't simply use the latest version of ruby. Then you have things like Jruby which is incompatible with some of the libraries designed for MRI. So, being able to segregate rubies is essential.

NatW 11y ago

I've been perfectly content using RVM https://rvm.io/ https://rvm.io/ - with all the functionality I need, and reliability, too. What am I missing out on?

elliotec 11y ago
Rbenv is much smaller and only does ruby version changes and installations with the ruby install add on. rvm is bigger and has more features but is a bigger pain to use in my experience.
- lucaspiller 11y ago
  Also the whole Gemset thing is basically redundant now Bundler has become the standard way of locking dependencies (Gems).
technion 11y ago
I fell on rvm because it seems to be the "default" recommendation. I don't see a need to use something "better" if the raw tool does the job perfectly. I do get annoyed that "rvm list known" tends to only show old versions. For example, it suggests it can install ruby-2.2.1, but I'm fully aware 2.2.4 is available, as is ruby 2.3 now. And for me at least, this problem is consistent after applying the standard advice of "get the latest rvm".
- aaronbrethorst 11y ago
  rvm was perfectly happy to install Ruby 2.3.0 for me this morning, upgrading me from 2.2.4, which is what I was using until last night.
- mwpmaybe 11y ago
  rvm "stable" hasn't been updated in quite a while, last time I checked. you need to install the "dev" version.
regularfry 11y ago
The problem with rvm was always that it tried to do too much. With a tool like that, as long as it's working, you won't see the downside. When it breaks, it breaks in complicated, hard-to-debug ways. If you're saying it's reliable for you, that's great. That wasn't my experience.