When I use your library, deploy your app, or run your tests I may not want to use rubygems. When you “require ‘rubygems’” in your code, you remove my ability to make that decision. I cannot unrequire rubygems, but you can not require it in the first place.
RTomayko: Why You Shouldn’t Force Rubygems On People
Good points: I never thought about the issue and I’m definitely guilty on the same behaviour. Seems Coral proposes itself as a possible solution, but I yet have to check whether it’s a viable one.
