Linked by snydeq on Mon 25th Oct 2010 21:23 UTC
Permalink for comment 447256
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Linked by Thom Holwerda on 04/16/13 9:29 UTC
Linked by Thom Holwerda on 04/15/13 22:44 UTC
More Features »
Sponsored Links



Member since:
2009-11-11
Perhaps the problem isn't so much OOP as its evangelists. There's no problem with everything being an object, so much as being forced to write code in what people consider "proper" OOP style (often in a high-mutation style, where accessors are mandatory even for simple data structures, like linked list items).
There's no reason why OOP can't be used in a functional style (immutable objects) or work nicely with other styles of coding (smalltalk, for example, is a lot more "functional" than python). Languages like F# and Scala show that these approaches don't have to be at odds with fp.
That's not to say that OOP is worthless. http://www.cs.utexas.edu/~wcook/Drafts/2009/essay.pdf
is a good essay on the comparison of OOP with more traditional abstraction techniques, although it perhaps requires a bit of functional programming knowledge.