use Perl

• Does it add value to the example ? (Score:1)

  by essuu (3384)

  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
  • Re: (Score:1)

    by jk2addict (4946)

    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.
  • Re: Speed of Moose (Score:1)

    by Stevan (6065)

    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
• My totally unbiased opinion ;) (Score:1)

  by Stevan (6065)

  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 :)

  Pros

  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