[Perl] combines the power of C with the readability of PostScript. -- Jamie Zawinski

@ColinTheMathmo I developed #Perl quite a few years for a living.
This clearly showed, that the codestyle policies and their enforcement within a project/team makes all the difference for non-opionated languages like Perl.

Some of the best structured, most readable code I ever saw was in Perl - but at the same time, you can write valid Perl code which is indistinguishable from trying to #OCR paint splatters:
https://www.mcmillen.dev/sigbovik/

93% of Paint Splatters are Valid Perl Programs | Colin McMillen

@ColinTheMathmo …and when it all goes wrong, there's a certain truth to this quote by Keith Bostic:

"Perl - The only language that looks the same before and after RSA encryption."

#Perl

@eliasp @ColinTheMathmo I suppose it depends on whether you like to form your own #programming opinions (individually or as a team) or whether you prefer them forced by the language itself

@eliasp @ColinTheMathmo BTW #Perl has two well-known tools to encourage and enforce #programming style and best practices, respectively:
#PerlTidy: https://perltidy.github.io/perltidy
#PerlCritic: http://perlcritic.com

Your project or team can use their reasonable defaults or further configure them to reflect and maintain the consistent application of your preferences. They also integrate with editors/IDEs, source control management, and author #testing.

@eliasp @ColinTheMathmo As an aside, it’s really strange when #developers that use #Linux and other #FOSS tools champion an ecosystem where a thousand distributions and desktop environments bloom, but in the next breath insist the best #ProgrammingLanguage is one that lashes them to One True #Programming Style.
@mjgardner @eliasp @ColinTheMathmo Don't forget CPAN::Audit to look for vulnerable libraries with open CVE's!