Re^2: Reflections on the design of a pure-Moose web app...

Two questions:

Isn't this something that could equally be done with standard (non-Moose) Perl objects?
What in particular does Moose give that enables this approach?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

Comment on Re^2: Reflections on the design of a pure-Moose web app...

Replies are listed 'Best First'.
Re^3: Reflections on the design of a pure-Moose web app... by locked_user sundialsvc4 (Abbot) on Mar 23, 2009 at 19:15 UTC
The distinct advantage that I found in using Moose was the ease with which the job could be accomplished reliably. The concept of “roles,” in particular, allows for a lot of useful functionality – in this case, particularly serialization – to be leveraged very easily and reliably. Since Moose is built on regular Perl 5.8, clearly anything that can be done in it can also be done without it, but this is a better mouse-trap.

Replies are listed 'Best First'.

Re^3: Reflections on the design of a pure-Moose web app...
by locked_user sundialsvc4 (Abbot) on Mar 23, 2009 at 19:15 UTC

The distinct advantage that I found in using Moose was the ease with which the job could be accomplished reliably. The concept of “roles,” in particular, allows for a lot of useful functionality – in this case, particularly serialization – to be leveraged very easily and reliably.

Since Moose is built on regular Perl 5.8, clearly anything that can be done in it can also be done without it, but this is a better mouse-trap.