title: Why should I care about RVM's Gemset feature when I use Bundler?
body: <p>I just don't get it. I thought, <em>Bundler</em> was developed to resolve version conflicts between gems. So that I just have to <code>require "bundler/setup"</code> and everything is fine, knowing that <em>Bundler</em> will load the correct versions of all my gems and their dependencies. Now, <em>RVM</em> is great for managing multiple Rubies, I know, but why should I care about the Gemset feature? Do I miss something here? Can it make my development even easier? Maybe, some of you can give me some hints on the perfect <em>RVM</em> + <em>Bundler</em> workflow for both, development and production.</p>
  
  <p>I also don't know when <em>RVM</em> starts switching to another Ruby. I know that I can have an <code>.rvmrc</code> file in my project, but do I have to <code>cd</code> to this directory so that the switch happens?</p>
  
  <p>Furthermore, I usually use <em>Passenger</em> for development since, thanks to the <code>Passenger.prefpane</code>, integration in <em>Mac OS</em> is great. Can I still do that with RVM or is there a better way to do it? Does <em>Passenger</em> recognize <code>.rvmrc</code> files and switch to the correct Gemset?</p>