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.
  • Practically everything he says here could apply to Perl, Ruby, Python, etc. as practiced by the average coder. His complaint about the "works for me" approach is not language-specific. He's really talking about the culture that has grown up around the language.
    • But as I read it, he's not talking about the average coder, but about the implementation. What you say is as if we'd judge Perl by the average beginning coder that still goes to use the old junk from Matt's Script Archive.

      No, this is about the implementors. And Perl is better in that regard. We have people who care about stuff working right, such as sub attributes, even if only 10 people in the world are actually using it. Gee, I don't know how many people do use attributes, but I am guessing it's far less than 1 in 100.

      That's a lot better than "buggy by design", which seems typical for PHP.
      • Indeed. What he's arguing for is, in essence, what Perl (mostly) gets right.

        That even if there's a dozen ways to do something, there should be A way that is a robustly correct solution to general classes problems, that is available, recommended, and isn't cumbersome to use.

        Think DBI and ? placeholders.

        You don't have to use them, but they are simple to use, strongly recommended, and solve the entire class of SQL injection attacks.