Re: Polymorphism Downsides (was: what's the future of Object Oriented Programming)
- From: "topmind" <topmind@xxxxxxxxxxxxxxxx>
- Date: 24 Sep 2006 21:33:44 -0700
Nick Malik [Microsoft] wrote:
"topmind" <topmind@xxxxxxxxxxxxxxxx> wrote in message
news:1158615511.931176.222270@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Phlip wrote:
I tend to ask "Have you read /Design Patterns/" as short-hand for "Have
you
seen examples of OO techniques being used correctly, to simplify
programs?"
Like I said elsewhere, the Design Patterns books is geared toward
systems software. It's lessons so far appear not applicable to other
domains, such as custom business software. I do not question OO's
abilities for systems software, but that is not my domain.
Well, you've answered my original question. Many if not most of the
examples of design patterns in the DP literature (both the DP book and other
books) use business software examples. Note: I consider systems software to
mean "operating systems" as in device drivers, hardware abstraction layers,
file storage drivers, system navigation and configuration functions, etc.
I do not consider graphics packages, personnel systems, inventory systems,
and the like, to be systems software. Examples of using OO in these cases
abound.
Note that I said *custom* business software. This would not include
graphics packages. Most businesses are not going to pay somebody to
build Adobe Photoshop from scratch for their internal stuff (yes, there
are probably rare exceptions.)
If they "abound", where are they?
So, the answer you gave is the one I expected: No. You have made no real
attempt to understand that which you criticize.
You have not pointed out specifics. Can you name at least 3 GOF
patterns that are shown with custom biz examples *in* the GOF book?
Look: I've listened to you, and tried to understand your viewpoint. I am a
fair person. On occasion, you make a good point. But most of the time, I
cannot imagine how you are drawing the conclusions you are drawing. I can
only assume you are considering different input than I am... or following
different logic. An understanding of Object Oriented software appears to be
one of the inputs on which our understanding varies. Perhaps our criteria
for a good result varies as well. I don't believe, from your words, that
you understand OO software. Perhaps I am wrong, but I do not believe that
to be the case.
You have not presented a single public-viewable example of OO being
better at custom biz-ware. I don't want to remenis about what I did in
1999. Why the hell should I? I cannot even spell remenis.
You have every right to be here, and to discuss issues as you do. However,
it is difficult to convince anyone, or even earn a minimum of respect, when
you speak poorly of techniques that you cannot speak well of.
Screw words then and show code. Show me OO code being better for custom
biz apps. If you cannot deliver, then we should part ways.
-T-
.
- Follow-Ups:
- References:
- what's the future of Object Oriented Programming
- From: VV
- Re: what's the future of Object Oriented Programming
- From: H. S. Lahman
- Re: what's the future of Object Oriented Programming
- From: Bruno Desthuilliers
- Re: what's the future of Object Oriented Programming
- From: Phlip
- Polymorphism Downsides (was: what's the future of Object Oriented Programming)
- From: topmind
- Re: Polymorphism Downsides (was: what's the future of Object Oriented Programming)
- From: Nick Malik [Microsoft]
- what's the future of Object Oriented Programming
- Prev by Date: Re: help me.
- Next by Date: Re: OO is not that great: many repeated codes
- Previous by thread: Re: Polymorphism Downsides (was: what's the future of Object Oriented Programming)
- Next by thread: Re: Polymorphism Downsides (was: what's the future of Object Oriented Programming)
- Index(es):
Relevant Pages
|