This might be the stupidest comment I've ever read on HN. There's not a single case where using Perl is the right call. As others have joked it's a "write only"language. The garbage you write in Perl is illegible to everyone else and will be illegible to yourself once you move on to the next project and have to come back and debug your old Perl in 18months+. You think you're being clever with your Perl one liners and mini scripts but you're actually sabotaging your team. My honest opinion is that anyone who knows this and still writes Perl needs to be fired because they're actively undermining the team and the organization with code that is essentially legacy technical debt the minute it's committed to the organization repos.
You use a real language for these projects because it allows someone besides yourself to collaborate and maintain the project
>>As others have joked it's a "write only"language.
The pet project you write to replace that Perl one liner is also write only once project. The only difference is you waste years of your life doing what we do in minutes.
There is nothing to boast about wasting your life doing things that don't even have to be done.
You use a real language for these projects because it allows someone besides yourself to collaborate and maintain the project