zlacker

>>todsac+(OP)
There was a lot of pressure in the Perl community to write things as succinctly as possible instead of as maintainably and understandably. That’s not realistic for use in a field with a lot of turnover and job hopping.

>>RayFra+P3
Yeah the joke was, Perl is write-only.

>>chrisw+W3
Write-only perhaps, but with perl you only have to write it once and it'll run forever, anywhere. No breaking on updates, no containers, no special version of Perl just for $application, just the system perl.

Because of this, in practice, the amount of system administration mantainence and care needed for perl programs is far, far less than other languages like python where you actually do have to go in and re-write it all the time due to dep hell and rapid changes/improvements to the language. For corporate application use cases these re-writes are happening anyway all the time so it doesn't matter. But for system administration it's a significant difference.

>>superk+K5
There was really only one big forced rewrite, 2->3, and ironically Perl was killed by failure to do the same with 5->6.

I agree that python versioning and especially library packaging is the worst part of the language, though.