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.

slowass.net, perldesignpatterns, perlsecurity.com, djbdns 3 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • "but the Perl community itself is atrophying, with knowledgable programmers jumping ship rapidly" Is that what you really think?
    • I don't see it myself.

      I see a small number of talented developers broadening their knowledge but none abandoning perl. You'd be a complete fool to discard a tool that works well and with which you've become an expert, even if you found some other tools that work nicely.
      --

      @JAPH = qw(Hacker Perl Another Just);
      print reverse @JAPH;
      • Oh yes, silly me. Market forces don't exist. I must be on crack. Programmers use whatever tool they think best. It would be a horrible world if we had to do things like walk into jobs where the language was already speced out by CTOs and project managers who based their decisions partially on following fads -- both towards technologies that get a lot of media and away from technologies that get a bad rap for being messy, unmaintainable, and having generally having been used by novices. Go talk to a recruiter. Ask him or her how many Perl jobs she has and then ask her how many Java jobs she has. Then ask how many C# jobs she has -- not that that many more people use C# but there are a hell of a lot of openings.
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.