Re: OO is not that great: many repeated codes
- From: Mike Austin <noone@xxxxxxxxxxx>
- Date: Thu, 28 Sep 2006 05:47:03 GMT
topmind wrote:
sjdevnull@xxxxxxxxx wrote:topmind wrote:Objects and classes are different things.Java is hardly a good role model here. Forcing everything to be a member ofIt appears that you are agreeing with the original claim that sometimes
a class is not the same thing as enabling elegant code.
procedural is less code than OO. Java is "bad" because it forces every
function to be a member of a class (or object)
It depends on the language and which definition of OO one is using.
Dynamic languages tend to make less distinction between classes and
objects. A "dynamic class" usually looks so much like an object that
one might as well make them an object to simplify the language rather
than support two almost-the-same things.
....called prototype-based languages. Self, NewtonScript, io, ...
Java sucks, lets move on.
Mike
.
- References:
- OO is not that great: many repeated codes
- From: Shawn
- Re: OO is not that great: many repeated codes
- From: Phlip
- Re: OO is not that great: many repeated codes
- From: topmind
- Re: OO is not that great: many repeated codes
- From: sjdevnull@xxxxxxxxx
- Re: OO is not that great: many repeated codes
- From: topmind
- OO is not that great: many repeated codes
- Prev by Date: Re: SOA and its real state of the art
- Next by Date: Re: SOA and its real state of the art
- Previous by thread: Re: OO is not that great: many repeated codes
- Next by thread: Re: OO is not that great: many repeated codes
- Index(es):