Comment on Don't overload #nil? in RubyComments−jasiek14yI guess that overriding the behavior of any built-in classes in Ruby is not a great idea, as most gems rely on that unmodified behavior.−DanielRibeiro14yAs a gem creator, is is terrible.As a application creator, is is only bad when/if you open source part of it. Otherwise, you can always run the gems' tests against the compillation of your env.−jaylevitt14yThere's talk of "traits" for Ruby 2.0 that will let you scope your monkeypatching.
Comments
I guess that overriding the behavior of any built-in classes in Ruby is not a great idea, as most gems rely on that unmodified behavior.
As a gem creator, is is terrible.
As a application creator, is is only bad when/if you open source part of it. Otherwise, you can always run the gems' tests against the compillation of your env.
There's talk of "traits" for Ruby 2.0 that will let you scope your monkeypatching.