Re:Ask HN: What is the state of the art in OOP?
by GVRV on Wednesday June 29, 2011 @06:58AM
(#2709025)
As someone working with Moose recently (and not really loving the experience), can you elaborate why it made your cut?
[ Parent
| on HN ]
Re:Ask HN: What is the state of the art in OOP?
by draegtun on Wednesday June 29, 2011 @08:03AM
(#2709161)
For my Perl reasons:
* Nicer to write than standard Perl OOP, ie. less boiler plate, quicker prototyping, covers bizarre corner cases, etc
* Moose is pretty much de-factor OO framework for Perl now, ie. big community drives its development and usage.
* Perl6 synergy, ie. Moose heavily inspired by Perl6. Makes it easier when I switch between writing perl5 & perl6 code.
For reasons why I think Moose makes the cut:
* Roles - ala Smalltalk traits. see http://search.cpan.org/dist/Moose/lib/Moose/Manual/Roles.pod
* Types - See http://news.ycombinator.com/item?id=1558882 (and also follow links back from it).
* Method modifiers - See my AOP comment elsewhere