Re:Ask HN: What is the state of the art in OOP?
by redthrowaway on Wednesday June 29, 2011 @05:01AM
(#2708818)
I find Python's OOPiness has a tacked-on feel, with copy.copy and self.x taking the place of more rational syntax. I've only looked at Ruby briefly, but it seems to be both lispier and oopier than python in an intriguing way. We'll see how I feel after using it in the real world for a bit.
[ Parent
| on HN ]
Re:Ask HN: What is the state of the art in OOP?
by beza1e1 on Wednesday June 29, 2011 @05:28AM
(#2708861)
What is tacked-on about this?
copy.copy: Who don't you "from copy import copy"?
self.x: It explicitly distuingishes between local variable and field access, which is the Right Thing in my opinion.
I do not understand, what this has to do with OOP at all.
Re:Ask HN: What is the state of the art in OOP?
by cies on Wednesday June 29, 2011 @05:53AM
(#2708905)
i get this tacked-on-OO-feeling when i do:
def something(self, ...) # inside a class
or
len(str) # instead of str.len (i know i can do str.__len__)
not very convincing reasons right? to me python has a strong foundation in OO. you want a tacked-on-OO-feeling? try php and/or perl :)
Re:Ask HN: What is the state of the art in OOP?
by CyberFonic on Thursday June 30, 2011 @08:26PM
(#2716360)
I think that the canonical OOP experience is with Smalltalk, e.g. Pharo which is far nicer IMHO than Squeak.