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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • The section on When Not to Use Perl reminds me of my favorite Larry Wall quote: "The trick is to use Perl's strengths rather than its weaknesses."

    Other than the first one, his arguments boil down to:

    2) Don't call external shell function when internal libraries are faster.

    3) Don't mix code with HTML.

    4) Don't write obfuscated code.

    Well, Duh! Sounds like good advice in any language.
    • Well, he hasn't even _touched_ real requirements for big projects. And why would he? If it comes to libraries, stability, deployment, toolchains, etc. there's not much difference between the languages, and CPAN is and always was a big win for Perl.

      He absolutely disqualified himself with this part:

      However, I would argue that more modern Web scripting languages, such as PHP and Ruby on Rails, offer more out-of-the-box Web support and a cleaner integration into the webpage experience.

      (Highlights are mine)

      --
      Ordinary morality is for ordinary people. -- Aleister Crowley