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 attitude where you "have to know how it works under the hood" or else you don't use it, is dumb, and leads to moronic efforts to reinvent wheels.

    Joel's buddy Jeff demonstrated this well when he decided to write his own HTML Sanitizer: http://www.codinghorror.com/blog/archives/001167.html [codinghorror.com]

    Engage cross-site scripting!

    And why are you whining about confess dumps? I presume because you are not used to seeing them, but the stacks are probably just as deep on most other modules you use, and you are oblivi

    • "The attitude where you 'have to know how it works under the hood' or else you don't use it, is dumb"

      When I hear about a perl module doing something whizzy, the first thing I want to know is if it's using a source filter. On top of all the other complaints you usually hear, source filters, even if they work correctly make it a pain to step through your code using the perl debugger.

      And Scott's main point here is that excessive dependencies can be a pain -- if installing Moose bugs you, then yeah, you want to know if you're installing something that uses Moose. (I used to think that deps were a non-issue now because we're all using CPAN.pm or CPANPLUS.pm to handle them automatically... I've gotten enough complaints to conclude that many people are still doing it manually.)