Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jk2addict (4946)

  (email not shown publicly)
AOL IM: chrislaco (Add Buddy, Send Message)
Yahoo! ID: (Add User, Send Message)

Journal of jk2addict (4946)

Friday August 25, 2006
08:42 AM

Who's Moose-ing?

[ #30750 ]

Before I embark on Mango with reckless abandon, I was thinking about possibly using Moose for it's non-Cat internals.

Who's using Moose out there? How's it going? Pros, cons, other? :-)

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • What's you're reason for using it, beyond that it looks like a cool idea (and it does, although I'm not using it myself :)

    It seems to me that Moose is a fast moving target and is changing rapidly. Will using it save you time and, more importantly, will it help or hinder the promotion of Catalyst/Handel in the wider community (one of the aims of the Mango project) ?

    My cautious side would say that it's adding another layer of learning & potential dependency problems and should therefore be avoided fo

    • Mostly for the before/after/around hooks to allow people to get at events. Sure, it can be done in other ways, but Moose seems the cleanest.
    • It seems to me that Moose is a fast moving target and is changing rapidly.

      Actually, Moose's internals are changing/improving rapidly, but it's outer sugar coating is pretty stable, and will not change without sufficient warnings if at all.

      Will using it save you time and, ... ?

      One of the more common reactions I get from people using Moose is how much (developer) time it saves them. I know for myself, it has made refactoring a large unweildy codebase a lot easier. In fact with that, most of my t

  • Well, my opinion obviously is heaily biased, however I am actually using Moose in real $work, so I figured I am still qualified to comment :)


    Well Moose takes care of a lot of redundant and tedious code (constructors, accessors, etc), basically making easy things even easier and much less tedious. Sure you could use the more standard solution of Class::Accessor, but that forces you to put Class::Accessor in your @ISA, and it does not initialize attributes for superclasses automatically like Moose