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 oblivious.

    Finally... surely the long dependency chain shows that the modules are used and maintained. A newcomer to CPAN has to base their choice from the multitude of Config modules (or whatever) on something, and the one the Moose/Catalyst/DBIC/POE folks use is probably a good bet.

    • I hate repeating myself. It never accomplishes anything. But I'm a fool. So:

      I *said* that all abstractions leak. Whether or not you agree with that, I did introduce that as a premise in what I wrote, I also make it clear why I need to know what's going on under the hood -- not because I care, but because it *breaks*. Or leaks, to honor the analogy. But if you didn't catch that the first time, I doubt you will this time.

      I am perfectly used to seeing confess dumps. They're usually 20 or 30 lines long f

      • Nice retort; proper old school, especially the bit about your manhood :-)

        Thanks for clarifying your point of view - I'd have preferred you to say some of this in a rather longer (and less vague) original blog post, which might have saved me the time in the first place of wanting to jump on your head. Perhaps take that as a tip for any future Moose musings here.

        At the moment I'm toying with Moosifying one of my own modules. It would make the guts so much more sane and manageable, but offer no real benefi

    • A newcomer to CPAN has to base their choice from the multitude of Config modules (or whatever) on something, and the one the Moose/Catalyst/DBIC/POE folks use is probably a good bet.

      To be fair, POE's requirements are quite lean. It only needs three nonstandard libraries as of Perl 5.8.9: File::Spec, Test::Harness and Test::More.

    • "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 wa