I have nothing against Mouse, but I'd like my app to run with either one of Mo[ou]se. For those applications wanting the lighter side of things, could we please make it a standard to use Any::Moose instead?
Really, I just want to choose which backend to use myself, rather than having to deal with two of them.
Please?
P.S., I've written Module::Install::Any::Moose for this kind of thing.
I pointed out a couple of weeks ago on a thread you started [1], that Any::Moose really doesn't seem to be able to solve the problem that I perceive is claimed of it.
Under what circumstances will a CPAN module switching to using Any::Moose help?
[1] http://lists.scsys.co.uk/pipermail/html-formfu/2009-March/001834.html
>
Take the instance that one of your dependencies starts using Moose: unless you get really lucky and it happens to load before anything using Any::Moose, then the only way to ensure Any::Moose correctly uses Moose rather than Mouse is to keep track of all your dependencies, and every time you update any cpan module, check whether 'Moose.pm' has sneaked into your %INC.
And then add "use Moose" to your main program, to ensure it's loaded before any "use Any::Moose" statement.
Now, if you have a thorough application test suite which you run after any upgrade, it's arguable whether or not it's really a problem that parts of the code uses Moose, and other parts Mouse.
But I would argue that Mouse + Any::Moose only have a legitimate place in end-users' application code, and not cpan modules.
Re:What problem is Any::Moose trying to solve?
lestrrat on 2009-03-24T15:29:31
Before I go either side, which of Mouse or Moose alone makes more sense than using Any::Moose? Just checking.
