As of late, I think Perl has gone more in the Python direction, and Ruby has gone more in the "old Perl" direction. (It is mildly amusing to watch the Ruby community make all the mistakes that Perl made 10 years ago, especially with its advocates' constant hatred for Perl.)
I recently had to explain to someone what "_" means in Perl (not to be confused with $_ or @_). It was simple for me to answer, because I had the experience. But someone seeing it for the first time wouldn't exactly be able to Google it, or look it up in a man page; who would think to look for it under "perldoc -f stat"? What's more, this particular short-cut, while useful, has a side effect: if someone maintaining the code inserts a stat on a different file in between the original stat and the "_", then the source of the "_" changes. For a single character in a script, that's a heck of a lot of barriers for a new programmer.
Pretty much everyone I work with has been burned by being handed some legacy Perl to maintain and as a result we are very reluctant to do any new work with it. The payoff for rewriting in Python is that the technical debt incurred for using Perl in the first place is repaid.
If you choose not to take advantage of those tools when writing a Perl 5 application, you bear the risk yourself. How does that reflect on the language or the ecosystem?
Most of Perl's bad reputation (e.g. that it's a "write only" language) is simply because the community around the language reinforces that style of coding.