Bug #52336 for Mouse: Friendlier guts for tweaking

Show quoted text
Not at all. You are assuming that people use Moose because they need all of its features and heft. I am assuming most people use Moose because they don't know about Mouse or Any::Moose. Therefore, the *end user* should have the ability to force code to use Mouse if they want. If it blows up because Mouse is missing something, they'll know not to force it. If it works as expected (which seems the more probable case), they've saved themselves from being gored by giant antlers :-P -- Free map of local environmental resources: http://CambridgeMA.GreenMap.org -- MOTD on Setting Orange, the 43rd of The Aftermath, in the YOLD 3175: It is wildly, crazily, stupidly, cross-eyed-blithering-insectly wrong! --DNA

Okay, I understand. I'd still tend to go the other way, and have provided a simple "Any::Moose::Forcefully" on the advent calendar's entry about Mouse: http://www.perladvent.org/2009/1/ Cheers! -- Free map of local environmental resources: http://CambridgeMA.GreenMap.org -- MOTD on Sweetmorn, the 44th of The Aftermath, in the YOLD 3175: sex, drugs, rock & roll chips, dips, chains, whips you know, you're basic highschool orgy kind of thing

Show quoted text
What a helpful response. Thankfully Mr. Trout provided explicit details about the misunderstnadings and short-comings of the initial draft. The entry has since been updated to address them. -- Free map of local environmental resources: http://CambridgeMA.GreenMap.org -- MOTD on Sweetmorn, the 44th of The Aftermath, in the YOLD 3175: sex, drugs, rock & roll chips, dips, chains, whips you know, you're basic highschool orgy kind of thing

Show quoted text
Okay, sorry. I didn't check the date stamps, and it looked like your message had been first but lost in the shuffle. Show quoted text
4x are what the docs say, if one is able to parse that sentence as it was apparently intended (though I did not initially). Having various other time constraints, I didn't have a chance to test it myself, though we usually try to. If someone is interested in verifying those figures, Test::Aggregate could be helpful in accurately doing so. If Mouse's gains really are all in start-up, the disparity between run times of Mo[ou]se with a common test-suite should largely disappear. Show quoted text
I suppose it can be seen that way, but it was meant in the light of giving power back to the end user, who ultimately has the right to do what they please with the code they choose to run. Indeed, someone else has commented to me that with the ability to forcibly use Mouse, they may be able to adopt the general OO framework of Mo[ou]se "ten years earlier;" they work for a large and very conservative business. Perhaps a bit of an exaggeration, but the general idea remains. It's easier to concvince the powers that be to review/test/install a single, smaller module than a dozen that are twice the size. Might they occasionally run into problems with code that was written against Moose? Sure, but at least they have the option of using those that don't but still say "use Moose" rather than "use Any::Moose" without waiting for them to be patched, or developing their own packages. Or, with it's foot in the door, Moose would have a leg-up on being accepted to address Mouse's shortcomings. In any event, I'm glad things are more less settled, and I can move on to more pressing matters. Sincerely, Jerrad Pierce -- Free map of local environmental resources: http://CambridgeMA.GreenMap.org -- MOTD on Sweetmorn, the 44th of The Aftermath, in the YOLD 3175: sex, drugs, rock & roll chips, dips, chains, whips you know, you're basic highschool orgy kind of thing