Linked by the_randymon on Tue 1st Jan 2013 19:11 UTC
Permalink for comment 546824
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
More Features »
Sponsored Links



Member since:
2009-06-30
You have listed all main reasons I've started using Perl back in late '90s. Yes, it's a perfect glue code. Yes, we have shell scripts but they are a fragmented, incompatible, unportable, inefficient mess. There *is* Perl on Windows and for the most part it is just - Perl.
After a brief experience of writing shell scripts on Linux and trying to deploy them on Solaris I took Perl and it has never fail me since. It is a weird and ugly language but it does its job extremely efficiently (easy to write non-trivial scripts) and is very portable and maintainable. Most of my scripts from a decade before still work and can be used on every single machine I have access to.
Nowadays, I also prefer Python - it's simply a better designed language. But it isn't as reliable and robust as Perl. Primarily because it's being rewritten over and over. This means that virtually all Python 2.2 and 2.4 installations (the only versions I can find in the office) are almost unusable.