I've always really liked the ideas of Modern::Perl, however I always hated the implementation. Something about a Modern::Perl hosted on CPAN, that didn't make use of CPAN seemed laughable to say the least. I set out to fix this. My new module nextgen, sits somewhere in between Modern::Perl and perl5i. It's based off of my subjective experience of what the best module on CPAN would consist of /today/.
It makes one bold assumption that isn't present in perl, or other like modules: the package's default meaning is "Class", unless you
use nextgen mode => ':procedural'
[download]
I find for myself this is true 99% of the time. Furthermore, I find that when I'm writing classes I want Moose. Spoiler: the other modules this enables are namespace::autoclean, autodie (core in 5.10 anyway), indirect, mro, utf8, strict, and warnings. And, when run with -M on the command line, oose.
I'd write more about it here, but I've already written a decent bit about it on the pod, check out nextgen and tell me what you think.
In reply to Writing a better Modern::Perl
by EvanCarroll
Deep frier
Frying pan on the stove
Oven
Microwave
Halogen oven
Solar cooker
Campfire
Air fryer
Other
None
Results (322 votes). Check out past polls.