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
Why not Moose
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Why know how it works under the hood? (Score:1)
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
Re:Why know how it works under the hood? (Score:1)
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.
Reply to This
Parent