Yeah, how dare you people point out that they're wrong. How dare you people point out their ignorance and where to remedy it.

We should coddle them and inculcate their incorrect notions and ignorance. Perish the thought that they should be pointed to the ample documentation where they can help themselves and improve in the process. Everyone should be spoon fed whatever they need immediately regardless of the effort they've exhibited. Otherwise it might mortally wound their fragile self esteem. Or they might get the idea that programming is an intellectual endeavor with certain inherent rigors. Perish the thought.

Shame on you all.

What? . . . Oh, sorry. Sarcasmometer was set to 11. Let's just dial that back a bit, shan't we?

I've never seen anyone go apoplectic over "PERL". This is apoplectic:

GOOD FRELLING GRIEF, WHAT KIND OF FRAKING MORON ARE YOU! EVERYONE AND THEIR SISTER'S DOG KNOWS THAT "PERL" IS NOT AN ACRONYM YOU VACUOUS, TOFFEE-NOSED, MALODOROUS PERVERT! IT'S "perl" OR "Perl" YOU SECOND HAND ELECTRIC DONKEY BOTTOM BITER!

This is what usually happens:

"Perl" is the language, "perl" is the implementation; "PERL" is just wrong.

See the difference?

As to being told to RTFM, most of the time that's probably because:

• the querent asked an extremely trivial question
• the querent showed no effort on their part to begin with
• it's an extremely simple question to begin with
• TFM answers said question rather succinctly to begin with (that, you know, kinda being the purpose of having good documentation)

The few times I've gotten RTFM'd on a couple of the Ruby IRC channels it's shown me where to find TFM that I wasn't aware of (things like ri or the standard library docs online). An RTFM is also a form of teaching you how to fish for yourself.