You can get a good overview of what Moose does for you on a large project from Ovid's blog where he discussed Moose as he was learning it. Let me grab a few relevant entries:
http://use.perl.org/~Ovid/journal/38649 http://use.perl.org/~Ovid/journal/38662 http://use.perl.org/~Ovid/journal/38705 http://use.perl.org/~Ovid/journal/38880 http://use.perl.org/~Ovid/journal/38785 He then encapsulated a lot of this into one presentation at http://www.slideshare.net/Ovid/inheritance-versus-roles-1799996. On Tue, Feb 1, 2011 at 7:03 AM, James Eshelman <[email protected]> wrote: > There've been fairly frequent references to and praises for Moose on this > list. After reading some of the doc and discussion of it, I'm still wondering > about a couple points: > > - Would it be accurate to say that using Moose will save you coding time (on > a large project, after learning it) but cost you significant runtime? > Always, sometimes, never? [Of course the frequent comment over the years on > this list is that if RT performance is paramount then don't use O-O perl at > all. Probably still true, but assume O-O perl is a given.] > > - What valuable O-O feature(s) does Moose provide (if any) that couldn't be > coded by a skilled programmer in perl? [There's some C programming/symbol > table manipulation under the covers?] > > TIA, > > Jim Eshelman > www.nepm.net > Network Monitoring with a Difference > > _______________________________________________ > Boston-pm mailing list > [email protected] > http://mail.pm.org/mailman/listinfo/boston-pm > _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
