tags:

views:

142

answers:

1

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:

Preferably, we keep these to modules people use but shouldn't. If the module isn't used by one author other than the creator then I don't really care.

A: 

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

daxim
Mouse and Mousse aren't really lookalikes as much as different implementations of (subsets of) Moose designed for particular system constraints.
Ether