> Every programmer who loves Perl should ask him/herself
I think this should read "Every programmer who loves any technology should ask him/herself [...]". Asking this question may be a great way to learn more deeply about the technology. I don't think that Perl is special in this regard.
> Is this a case of Stockholm Syndrome?
Not if the programmer acknowledges there's problems with Perl, but loves it anyway; not if the programmer has experience with other technologies that have different strengths and weaknesses.
I disagree. Just as it allows you to write horrible stuff, you can just as well get your shit together and do it maintainable, robust and nice to the eye :)
And as the author states, you (almost) always have an choice to run other languages, where perl runs. Not really a hostage situation, methinks.
Edit: Not that I particularly like Perl, but neither do I hate it. I think it's somewhat bad reputation stems more from the fact, as described above, that it forces you less to do things nicely and is very accessible to the, let's say, less experiences programmers - so a lot of quickly cobbled together stuff flies around.
Many years of programming practice and SE theory have taught some of us that discipline is not the main concern of most programmers and the higher a level you require of it, the more you will be disappointed. Which means that you tend to get more maintainable results from languages which either require very little discipline to produce good code or those that strictly enforce discipline (e.g. Go).
Sadly, even the code on CPAN (which was built to withstand some scrutiny apparently, or why else would anyone release it to the public) is often so badly written that I wouldn't want to debug or maintain it.
> And as the author states, you (almost) always have an choice to run other languages, where perl runs. Not really a hostage situation, methinks.
In practice you're more likely to find old, hard to maintain Perl code bases that noone is able or wants to rewrite in another language, if you get hired to program in Perl. If there was a realistic choice to use another language, it was likely made already years ago.
Having worked in several corporations now I have to respectfully disagree. My experience is that either the code base was scheduled to be retired (but we all know how that usually turns out: the app is used for at least 3x(abs($retiredate - $now)) + $rand ), nobody could be bothered to keep the system current, or there was always something more important to do (which overlaps a bit with the second point).
Come to think of it, I really can't come up with a situation where you can't replace perl with a reasonable amount of work? But then again, I'm not active in the perl field.
Apparently the math libraries written in fortran back in the day have become such a foundational part of analytics, that nobody really wants to re-implement them.
On the other hand, the API is not something that is subject to change. A lot of software expect this to be stable, like Matlab, R, Octave, Numpy, and a lot of others.
I haven't touched Fortran in 20 years though :) I loved me Pascal except the semi-colon key broke on my keyboards.
Fortran compiler. There are no Fortran interpreters in existence, anywhere, that I've been able to find. For FORTRAN 70, Fortran 90, or any other versions. If someone manages to find an interpreter and proves me wrong, I'd love to hear about it.
That'll show me to rely on my hazy memory of something I read five years ago on wikipedia =)
That said, I'm also not aware of any Fortran interpreters, and it would surprise me if there is one.
(And yeah, 10+ years old Perl code bases might be less than pretty... The environment evolves quickly, for good and bad.)
Please excuse me for being an idiot, but I don't see the problem.
Just because something is locally good doesn't mean there isn't a more optimal good elsewhere.
(For those of you who only know Walter Mitty from the Ben Stiller movie, here's the original short story: http://www.newyorker.com/archive/1939/03/18/390318fi_fiction...)
I think for me it was. The jobs kept coming, stuff kept getting done, I enjoyed myself, I'm proud of most of the code I wrote, and yet, it never felt completely right. Probably because Perl has always been more of a petri dish for idioms than an organized home for them.