On 2011.11.22 11:22 AM, David Golden wrote: > On Tue, Nov 22, 2011 at 2:02 PM, Eric Wilhelm <enoba...@gmail.com> wrote: >> Is there a way to remove some of the work Mouse is doing at startup? >> What is it doing? > > How much of Mouse is needed? Could Moo be used? (I ask without > having read the details of the OO breakdown of TB2)
No. Moo has runtime dependencies, is harder to bundle (multiple files), is not upward compatible with Moose (their type system is incompatible), lacks Moose types, a class can't use more than one role at once, and has no meta system. And it's slower at runtime. I'm also not convinced of Moo's stability. Mouse has strictly adhered to being a subset of Moose. Moo hasn't. The Mouse folks have said they'd test vs Test::Builder2. Finally, Moo has only existed for a year. About the only advantage is Moo loads about 10ms faster than Mouse/XS. The major Mo[ou]se features that Test::Builder2 uses heavily is roles and attributes. It also uses types, coercion, meta classes and method modifiers, but those could be removed if necessary. I've tried to keep it simple to avoid touching any actual or potential Mouse bugs. -- There will be snacks.
