If you're going to be in the tiny tiny minority of Ruby devs that insists on not installing rubygems, having a stubbed "rubygems.rb" in your load path is not an unreasonable request --- particularly compared to the request that everybody else uses some contorted command line to execute their script to accomodate you.
It's unreasonable if you want to have both rubygems and some other package system available at the same time, as is most often the case. Having to use the contorted command line is the rare case, as you almost always invoke ruby scripts through the rubygems generated wrapper or some other isolated script intended specifically for command line use, which takes care of rubygems itself.
