The view many have of Perl is of Regular Expressions. They are powerful, but they are hard to read. With Regex in Perl, you can have whitespace and comments to make readable expressions, but with the Perl-Compatable Regular Expressions (PCRE) you see pulled into other languages, you often don't.
Another source of bad views of Perl is Brad's Script Archive, which is what people had before Stack Overflow. Except Brad's Script Archive was horrible Perl in the context of 1990s Perl, and with Perl Critic, Perl Best Practices, Modern Perl and others, Perl today is far better.
But because of backward compatability, that crap Perl still works.
I wouldn't necessarily advocate you learn it if it doesn't make sense in your environment, but I don't think it's a bad language.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
At work there is an application under active development (new features, not just bug fixes) that is written in ASP classic.
Every once in a while some manager will start making the rounds at cubicles and asking if anyone knows PERL or COBOL....
Perl isn’t terrible, cobol on the other hand....
I code Perl daily. It can be written well.
The view many have of Perl is of Regular Expressions. They are powerful, but they are hard to read. With Regex in Perl, you can have whitespace and comments to make readable expressions, but with the Perl-Compatable Regular Expressions (PCRE) you see pulled into other languages, you often don't.
Another source of bad views of Perl is Brad's Script Archive, which is what people had before Stack Overflow. Except Brad's Script Archive was horrible Perl in the context of 1990s Perl, and with Perl Critic, Perl Best Practices, Modern Perl and others, Perl today is far better.
But because of backward compatability, that crap Perl still works.
I wouldn't necessarily advocate you learn it if it doesn't make sense in your environment, but I don't think it's a bad language.