As a full time Perl developer at different times over that last 20 years (and the rest of the time a sysadmin with heavy Perl use), it's not that bad anymore. A lot of very poor quality Perl was common in the late 90's and early 2000's, but for the same reason a lot of very poor quality PHP code was around from the early 2000's to early 2010's, which is to say because a lot of novice programmers (or at least novice's to Perl) were writing it, and those novices also happened to to get a lot of code into production. In Perl's case it's because the dot com boom really elevated teh quick and dirty cgi script and Perl was the main language available for that.
These days, people that aren't novices tend program much more clearly in my experience, and there's style guidelines and code linters to take up the slack. It's not like other languages never have to deal with people writing odd or unintelligible code either, there's a reason why style standards are a big thing in many places. Here's an example of a module I use that I just looked up. It's fairly terse in parts (but it's a module, so I hold it to a different standard than my own code), but I would expect anyone familiar with perl would have zero trouble determining what's going on in here, and a lot of code bases will be a little more verbose or use more white space to error on the side of caution and help people process what they are seeing easier.[1]
1: https://metacpan.org/release/Path-Tiny/source/lib/Path/Tiny....