Ruby Require Order Problems « Katz Got Your Tongue?

@drbrain what do we need to make this happen? It's a real issue for me here:

Jonas Nicklas, Posted April 17, 2010, 8:44 am For once, I disagree ;) I don’t see anything wrong with load order being important for gems. CarrierWave has adapters for half a dozen ORMs, and they’re all required implicitely (if the relevant constant is defined). I’ve never had a single person complain about this or file even a single issue about it. If I can’t rely on load order, there’ll have to be an extra step of requiring the right orm extension. That destroys a lot of the “works-out-of-the-box” feeling, and gives me a significant disadvantage compared to other solution which haven’t bothered to implement ORM agnosticism. Essentially you’re discouraging one good practice (agnosticism) in favour of encouraging another (no load order). The problem is that having significant load order isn’t really broken in the real world. Lots of gems have it, lots of people use it, no ...

Full article: http://yehudakatz.com/2010/04/17/ruby-require-order-probl...