http://www.joelonsoftware.com/articles/LordPalmerston.html
Because, though this is a relatively sober and even-handed example of the genre, it still inevitably contains howlers like this:
Search for "rails". Most of these programmers will depend on one library, Rails, but then get the rest of their code by cutting-and-pasting from blogs.
Someone has never heard of gems:
http://en.wikipedia.org/wiki/RubyGems
Which is hardly surprising. This is the canonical problem with articles like this one: The guy doesn't waste time tinkering with Ruby, because he's busy being productive with Perl, so why should he be expected to know anything about how the Ruby community works?
(This is why I try not to write about Python except to assert that it must be one of the best languages in the world: I'm literally unsure how to write hello, world in Python, but smart people use it all over the place, so deference and politeness forces me to assume that it's utterly perfect until proven otherwise.)
Anyway, I'll help out by saying that I think jrockaway's point still stands, albeit on fewer legs than before: Perl is a considerably older language, its community is more experienced, it's (among other things) a traditional tool of system administrators -- who are, in my experience, relentlessly pragmatic people who crave stability, reliability, and clear docs -- and so it has had a lot more time and incentive to organize and standardize its packaging and documentation systems. Ruby does have docs difficulties, as do many open-source projects which have recently experienced explosive growth.