I stumbled upon a nugget of wisdom on this post answered by Hongli Lai on the Phusion Passenger Google group:
This is normal. On 64 bit all pointers are double the size. MRI is
implemented with a lot of pointers so all Ruby apps use almost twice the
memory. Go back to 32 bit if you don’t like this.
I recently did a fresh install of Ubuntu on a Dell laptop for a Rails project I’m working on. Everything was cruising along perfectly until I tried getting RVM installed, which I erroneously assumed would be a breeze. I kept bumping into issues where an installed gem was complaining that it wasn’t compiled against the correct libraries. For each error, I needed to invoke a special rvm package install uninstall the ruby, reinstall the ruby and reinstall the gems. It was turning into a nightmare.
It turns out that Chris Irish had a much cleaner approach: install all the libraries via apt-get and be done with it. Too simple. I followed the steps in his post and was rollin’ with RVM in no time. It appears that the following packages needed to be installed prior to installing the gems:
sudo apt-get install build-essential bison openssl libreadline5 libreadline-dev curl git-core zlib1g zlib1g-dev libssl-dev vim libsqlite3-0 libsqlite3-dev sqlite3 libreadline-dev libxml2-dev git-core subversion autoconf
Kerry Buckley put up a killer slide presentation on RSpec. Added bonus: he used Slippy, an open source HTML presentation framework, to create the presentation. Use the arrow keys to navigate or type a number + return to jump directly to a slide in the deck.
For quite some time, I’ve been using the open_gem gem. It’s a dead simple way to open a gem in your editor and if you subscribe to John Nunemaker’s approach to Stop Googling, it fits perfectly into the workflow.
From the command line, it’s simply:
Today, while reading bundler’s help file, I noticed the open command. It appears to do the same thing as open_gem, but without the need of an extra gem.
Now, I just type:
I love the world of ruby!