Given these assumptions:
- Your codebase is using
Moose.pm
- Minor changes in implementations do not warrant having conflicting functionality
What modules would you not want to see, by the very fact that Moose does that functionality better? This is for my recently released nextgen::blacklist I'll go first:
- NEXT
- SUPER
- base / parent
- mixin
- fields
- All of the Class::Accessor stuff
Preferably, we keep these to modules people use b开发者_运维技巧ut shouldn't. If the module isn't used by one author other than the creator then I don't really care.
hanekomu collected and compared accessor generating classes: http://hanekomu.at/blog/dev/20081101-1258-dissecting_the_moose_4-benchmarking_accessor_generators-accessors_only.html
There are a number of Moose work-alikes: Mouse, Coat, Gloom, Mousse
精彩评论