Most of the time I paste a one line "perldoc -f foo" reply it's because the entirety of the answer is in that part of TFM. A large part of getting really productive in Perl is to learn how to use perldoc effectively and where to look for what kinds of information (so that eventually they too can completely answer questions with a succinct two word perldoc perlzorch).

In fact I almost commented as much on the "Hey, let's rewrite perldoc" Discussion the other day. It's not that the documentation is lacking, it's that people don't know where to come in because it's so complete. If you're dissatisfied with Perl's documentation, take a look at what comes with Ruby (disclaimer: I \N{HEART} Ruby; I just think that the current state of the documentation is miles behind Perl's (due in part to it's relative immaturity I'm sure)).

Update: Just to clarify: this is why I specifically said relative immaturity, and that statement was in regards to the Ruby documentation. The second edition Camel from which most of the core of perldoc is descended came out in 1996; the first major English Ruby documentation (in the form of the Pickaxe book) wasn't out until 2001. And while I also \N{HEART} Smalltalk and its class browser that Rdoc is modeled after, there are times and workflow patterns when perldoc -f foo beats the pants off start-browser-clickety-clickety-bring-up-find-pane-clickety-clickety.

Another Update: In the process of mucking with Ruby On Rails (which is pretty spiffy, by the way) I've become aware of the ri command which comes with recent (1.8+, I believe) Ruby which functions like perldoc -f for Ruby classes and methods. They're definitely catching up (and Ruby's really growing on me, which maybe means I need to see a dermatologist (or a geologist)).