Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Perl 5 Programmers Are Dying 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • My comment here ran a little long so I posted it independently. I am in a position of both loving Perl and actively working to extract it from the company I work at. This is heavily biased by my experience and dismay trying as best I can to fix serious problems at work. http://vocal-chord.blogspot.com/2008/12/perls-trail-of-tears.html [blogspot.com]

    • So I read your post, and apparently it will be unicorns and rainbows, if only sysadmins wrote software beyond their ability in python instead of perl ?

      You stated at the start of your blog entry that the problem was sysadmins doing the jobs of programmers, wouldn't it be better to hire programmers who know perl to do the programming and keep the sysadmins to sysadminning ?

      Python won't enable them to program an iota better than perl, heck they'll probably try and apply perl, shell and c idioms to python and that would be an even worse trainwreck than what you have now!

      --

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.