NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Success Stories (Score:2)
Perhaps you could get her to mention that.
Reply to This
Re:Success Stories (Score:1)
Hard to read = "Only if you don't comment your code and don't write documentation, but then only bad programmers don't comment or document their code"
The job security thing is also a myth, anyone that thinks so deserves to be fired.
More perl in aviation (Score:2)
So much for the old "perl isn't fit for mission critical software" - our briefing system meant that one of our customers was the only european airline able to get it's customers to their destination for a couple of days last christmas, all the others had their customers stranded at airports.
@JAPH = qw(Hacker Perl Another Just);
print reverse @JAPH;
Re:Success Stories (Score:1)
I guess you _could_ assume that the site just creaks along on badly written perl, without seeing the code you wouldn't know it's all Object Oriented, with thousands of tests, optimized caching (both on disk and using memcache), documented and reviewed by another developer before going live, all automatically deployed on multiple servers using an automated packaging syst