It's like slang in code. Outsiders have a hard time understanding, but those in the crowd and culture know it well. Sometime's it gets flaunted, like the "cool" kids who need others to know they're cool, but sometimes it just slips out. Most people here helping others make pretty clear code in examples, as I'm sure books do. Personally, I know I tend to abuse $_ more than neccessary.
Perl is an interpreted-ish language, so that means most of it's work is done either via the web, like cgi or mod_perl, or completely in-house projects, where you know you'll have the proper environment. Sure, you could use PAR and make executables, but it's still pretty rare to see such programs about. It's popular amongst system administrators since it takes the task of shell, sed, and awk pretty well (and brings the power of those tools to Windows).
It's a fun language to use and learn. It's set up so that all you have to learn is the subset of the language you're going to use. You can have two expert perl programmers that don't know each others' skill set at all.
So much of Perl's power comes from CPAN.org, a huge archive of free to use code. Bets are good if you have a strange task to do, you're not the first, and someone's written a module to do the bulk of it. It's an amazing time saver. Connect to your databases with DBI, then change database servers. You often only have to change the connect line in your code, the rest works the same because DBI makes the conversion transparent.
I guess the question is, what do you want to do with Perl? While I'm sure Perl can do it, it may not be the right tool for you.
________________________________________
Andrew - Perl Monkey