I wrote code for a bank using perl. I'd say 95% of their code at the time was in perl. Website called perl, back-end processing was perl scripts. Cron jobs were all perl script that needed to run to do house-keeping.
I personally really like Perl. It does kinda encourage code-golfing, but that's what makes it so nice for one-off scripts.
As Perl grew up, the idea of "you have tests for at least basic stuff" was built into the culture. For example back in the mid-90s it was expected that every module came with a test suite, and every site would run that test suite before installing the module. When you went to package something for CPAN, you were expected to have a ./t directory with tests, and there were lots of examples to show you how to do it. And automated scripts that expected you do to it.
It was something like 15 years before anyone thought of naming the test protocol. It was just how you did things.
And thus the inspiration for Perl :)
(Edit: disappointed to see the Perl link doesn't actually work).
Perl is still one of the most widely used languages in world today.
I think it's safe to assume that the people choosing not to use perl have a good enough reason for their decision.
50% of my (new) projects remain in Perl. The other 50% in a mixture of C, Go, and C++.
I design semiconductors and every week I have to write a couple of small scripts to process text files or reports and that is always in Perl. Everyone at work knows Perl. Those that don't learn it.
The EDA tools mostly use Tcl as the internal scripting language so I have to use that.
I have no problem with new languages but I find regex's in other languages to be too verbose.