News for hackers. Stuff that matters.
Re:Ask HN: What is the state of the art in OOP? by draegtun on Wednesday June 29, 2011 @05:25AM (#2708856)
I'd say CLOS (http://en.wikipedia.org/wiki/Common_Lisp_Object_System) & Moose (http://moose.perl.org) myself.

However I do like Prototype based OO (http://en.wikipedia.org/wiki/Prototype-oriented_programming) and especially its implementation in Io (http://www.iolanguage.com)

Re:Ask HN: What is the state of the art in OOP? by billitch on Wednesday June 29, 2011 @05:42AM (#2708886)
Well, CLOS may be state of the art in very fine designed,exhaustively redefinable, roll-your-own aspect oriented programming, and the most exhaustive object oriented paradigm for the most fluid pragmatic language ever.

But I doubt you'll find useful sources for programming style searching for it.

If you are implementing an object-oriented paradigm for your programming language, it's a very recommendable source to discover what can possibly be done with OOP.

Re:Ask HN: What is the state of the art in OOP? by draegtun on Wednesday June 29, 2011 @06:13AM (#2708946)
But I doubt you'll find useful sources for programming style searching for it.

How about AOP? (http://en.wikipedia.org/wiki/Aspect-oriented_programming). I think both CLOS & Moose push you more towards this programming style.

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?
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