I can write Perl. Okay-ish. But I can almost never read Perl. I mean, I can read my Perl, 75% of the time, but other people's Perl? Very difficult.
Managers (wisely) know that a large important project isn't (shouldn't be) built by one super-star programmer who then decides to leave for greener pastures, but that it's read, often times more than its written, by a team of people. Readability > Writability.
And so Perl was destined to "fail" in the corporate world, at the expense of more boring languages like Java/C#.
Of course there's exceptions and I'm sure there's 2-3 companies still out there that run Perl exclusively, but ultimately, it's a "bearded-loner-sitting-in-the-corner" language.
Without saying what your level of expertise is, and showing a sample of your Perl, drawing any conclusions from your statements is like reading tea leaves.
Readability, of ANY code, is more often than not determined by how good the author is at naming things and avoiding senseless repetition (which are both skill honed with experience), and much less by any given feature of the language itself.
Managers (wisely) know that a large important project isn't (shouldn't be) built by one super-star programmer who then decides to leave for greener pastures, but that it's read, often times more than its written, by a team of people. Readability > Writability.
And so Perl was destined to "fail" in the corporate world, at the expense of more boring languages like Java/C#.
Of course there's exceptions and I'm sure there's 2-3 companies still out there that run Perl exclusively, but ultimately, it's a "bearded-loner-sitting-in-the-corner" language.
Not that there's anything wrong with that.