![]() It has an interesting design where installing new versions does not require to update ruby-install. Ruby-install is the simplest Ruby installer. Does not install system packages on its own (but that is more future-proof, and building Rubies tend to fail clearly when there is missing dependency).The release process is entirely automated (kudos to does not install system packages for you,īut documents them on their wiki, which I find is much more future-proof. This is great to also ship bug fixes quickly. Users update ruby-build regularly as that is the way to get new versions. The design is really straightforward (one definition per Ruby version), and as a result it’s much more reliable. It also offers -dev versions, which is incredibly useful to let users check Ruby implementation bug fixes, or simply to try the latest/fastest/best build of a Ruby implementation. It offers a wide choice of Ruby versions. Ruby-build is the best-maintained Ruby installer.Īctive maintainers include from the CRuby core team, others and myself. Huge (25000 SLOC of Bash), hard to maintain, and due to that many bugs.The built Ruby can differ quite a bit from a standard build, which can cause extra issues.Binary builds of some CRuby versions on some platforms.Support the most Rubies, even very old ones (some with patches).Automatically installs system packages for many platforms.More platforms can be nice for beginners, but platform-specific code eventually always breaks due to incompatible changes in operating systems (e.g., package names). To be fair, RVM served me well at the time other Ruby installers/switchers did not exist. Which I really dislike as a Ruby implementer because it tends to break things in subtle ways (this behavior was later disabled when installing TruffleRuby). I had many uncertainties, and the large codebase plus a lot of global variables made it really tricky.Īs a result, there were multiple bugs and a lot more effort than for other Ruby installers.Īlso, RVM actually changes standard Ruby executables like rake, To give an idea, when I added support for TruffleRuby in RVM, Some features like gemsets seem much less needed nowadays as there is Bundler. To keep correct (note: I’m not counting test SLOC). Than all the others (25000 SLOC of Bash), and that makes it hard to maintain and That’s actually a doubled-edged sword, as it means RVM has a much larger codebase RVM is probably the oldest and certainly the TLDR: feel free to jump to the Conclusion and Recommendation. I am not reviewing Ruby installers or switchers for Windows as I have no experience with them. I contributed to all 3 Ruby installers when adding support for TruffleRuby,Īnd so I have experience both with their codebase and their usage. Type “gem browser” and enter.In this post I review the most popular Ruby installers (making it easier to install a Ruby)Īnd Ruby switchers (to switch between different Rubies conveniently). When the packages load, another selection window will appear. Once you see “Package Control: Install Package”, press enter. In ST2, press “cmd + shift + p” and then type “install”. Once you choose a gem of the list, this plugin will open the source of the gem in a new window with the code ready for inspection and EVEN modification in real time (useful for debugging). ![]() It will list all the gems that have been installed via bundle for the project folder.Once you see “Gem Browser: List Gems”, press enter.In ST2, press “cmd + shift + p” and type “list gem” (or ctrl + shift + p if you're on Windows or Linux).Tested on OSX with RVM, Xubuntu with rbenv and Windows with RubyInstaller How to Use When you select a gem, a new Sublime Text 2 window will open with the code ready for inspection. This plugin allows you to quickly access the code of a gem that you have installed via Bundler in the current project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |