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

use Perl Log In

Log In

[ Create a new account ]

Aristotle (5147)


Blah blah blah blah blah []

Journal of Aristotle (5147)

Friday April 15, 2005
03:00 AM

Idle thought

[ #24202 ]

A thought that just struck me after reading milardj ’s Whuffie in Action and thinking about Perl’s “whuffie” outside the Perl community, how that appears to depend on vocal people’s emoting, even though every organization beyond a threshold size seems to rely on the trusty workhorse that Perl is:

“Perl’s problem is that it appeals to clever people. Perl’s strength is that it appeals to smart people.”

And I’m not so young anymore as to count myself among the smart people…

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • The first company that I worked at used a lot of awk scripts and one-liners. We ended up moving to perl due to some limitations of awk (if I remember correctly it had to do with the max size of records that awk could handle).

    When I moved to my second company perl wasn't used at all which is very surprising considering the code base was in the millions of LOC and a good portion of that was reports/extracts/loads. I promoted perl heavily from day one and after solving some internal requests with perl very

    • Oh, I know how that came to be. I also firmly believe that Perl, even as Perl5, will continue to be successful as a workhorse because it lends itself so well to small tasks. Only Ruby comes close; Python is not going to steal mindshare among those who frequently write very short, disposable code. Once you’re catching small fish with a tool that’s capable of hunting bigger ones, you’re likely to use it lots.

      However, all of that really is tangential to the main point I was pondering, which