Stories
Slash Boxes
Comments
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

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
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

    • 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 time has been spent removing code that Moose can handle is much fewer lines.

      My cautious side would say that it's adding another layer of learning & potential dependency problems and should therefore be avoided for this particular project.

      Well, I know many of the Catalyst folks have been looking at using Moose, so it the "another dependency" issue is moot if/when that happens. As for the learning curve, Moose (IMHO) should actually make it easier, especially for a non-perl audience who are used to a proper object system.

      - Stevan