James, I know others have replied already, but my experience with Moose is that:
1) the penalty is only on startup time. It's not an issue for a long running application. 2) the features you gain from moose (roles, native trait handling, type checking) more than compensates for the time spent learning moose. IMHO your code also becomes much more maintainable, because the boilerplate code (accessors, constructors, etc) simply goes away, leaving you to focus on the important bits. Drew On Tue, Feb 1, 2011 at 3:03 PM, 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?] > _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
