Linked by snydeq on Mon 25th Oct 2010 21:23 UTC
Permalink for comment 447267
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/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
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
More Features »
Sponsored Links



Member since:
2009-11-11
I view "everything is an object" to mean that everything (or at least most things) is first-class: functions, methods, classes, etc. can all be passed around, and thus used much as "normal" objects. Smalltalk/ruby especially exemplify this, Java not so much (no first-class functions, etc. only reflection hacks)
I agree that not everything needs to be done through instanced objects, etc. However, it's nice to have OOP or something similar (haskell typeclass, etc.) when you do want it.
Inheritance has its ugly parts, especially in Java, but I don't view it as fundamental to OOP (or even classes, really). As Alan Kay said, it's all about the messages; OOP allows an object to be used elegantly without regards to its actual implementation.