Re: Module Bloat and the Best Solution

[dragonchild]

The key is the number of moving parts that you are responsible for. If the moving part is from CPAN, then you just care that it works. More importantly, you're not thinking on the order of the problem, but the solution.

Another way to think about it is this - Perl itself is a CPAN module. Otherwise, you'd be using C. C doesn't have memory management, but Perl does. C doesn't have scalars, but Perl does. C doesn't have a lot of what Perl does, which is why I use Perl - it makes my life easier. So, that's why I use CPAN modules. As many as I can possibly lay my little grubby hands on. I have my own "core" list that I install whenever I can so that all the tools I want to have are there.

[johngg]

Just out of interest, and if it's not breaking any trade secrets, what modules do you have on your "core" list?

Cheers,

JohnGG

[dragonchild]

These are the modules that I reach for first when trying to solve a problem:
• Scalar::Util
• Scalar::MoreUtils
• List::Util
• List::MoreUtils (This is just a phenomenal module)
• File::Slurp
• DBIx::Class
• Catalyst and, possibly, CGI::Application
• DBM::Deep
• Test::Deep, Test::Warn, Test::Exception, DBD::Mock (numerous others in this category)
• Set::*
• Algorithm::*
• Tree
• Template Toolkit, Excel::Template, PDF::Template, CAM::PDF, Test::PDF
• Moose

And this is just what I can think of in 10 minutes. Some of them are written/maintained by me and most have been contributed to by me or people I know. In addition to this list is a knowledge of how to navigate CPAN and whom to ask when I want to solve something.