News for hackers. Stuff that matters.
Re:Don't overload #nil? in Ruby by jasiek on Thursday November 10, 2011 @03:18AM (#3219403)
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.
Re:Don't overload #nil? in Ruby by DanielRibeiro on Thursday November 10, 2011 @09:06AM (#3220054)
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.

Re:Don't overload #nil? in Ruby by jaylevitt on Thursday November 10, 2011 @03:23PM (#3221691)
There's talk of "traits" for Ruby 2.0 that will let you scope your monkeypatching.