Earlier quoted context omitted.
I've been trying to hire a perl programmer for about a year now. It's just not where the smart people want to go with their careers, but we have a huge codebase built up in it, so we're stuck.
We don't have any trouble hiring Perl programmers. Maybe it's less about Perl and more about other aspects of the job, in your case? And oh yeah, I think I am offended by the "it's just not where the smart people want to go" comment.
There really isn't a reason to; the script languages that have come since then have fixed Perl's problems without losing any power. The only argument Perl has left is CPAN [1], but given the amount of duplication and bad code there, CPAN isn't as big as it's made out to be. I don't know about Ruby, but I used Python not so long ago and I noticed that not only did it have libraries for everything I needed to do, aside from DB access (which I had to download) they were all included with python itself. This is very nice in big organizations where downloading anything is a huge pain.
[1] Well, ok, it also has the COBOL argument of "there is a large code base out there to be supported" but I would expect this argument to only be compelling to the same people that were attracted when COBOL used it.