Let me preface this post by saying that I'm no Ruby expert.  I like it.
 It's fun.  But I won't claim extensive knowledge on it.

So when this guy blogs about a Python quality that he feel is better
than a Ruby quality:

    It's the second generation that's going to be less enthused,
    that's going to stare in bafflement at these classes that
    mysteriously spawn methods, and trying to figure out what's
    going when there's an exception in dynamically generated
    code. You can monkeypatch code in Python pretty easily, but we
    look down on it enough that we call it "monkeypatching". In
    Ruby they call it "opening a class" and think it's a cool
    feature. I will assert: we are right, they are wrong.

    -- http://blog.ianbicking.org/theres-so-much-more-than-rails.html

I am curious what this means.  Is Python against dynamic stuff?  And
Ruby for it?  And so we just agree to disagree?  Or do I misunderstand?

Just curious.

Drew