From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 109fba,b87849933931bc93 X-Google-Attributes: gid109fba,public X-Google-Thread: fac41,b87849933931bc93 X-Google-Attributes: gidfac41,public X-Google-Thread: 11cae8,b87849933931bc93 X-Google-Attributes: gid11cae8,public X-Google-Thread: 114809,b87849933931bc93 X-Google-Attributes: gid114809,public X-Google-Thread: f43e6,b87849933931bc93 X-Google-Attributes: gidf43e6,public X-Google-Thread: 1108a1,b87849933931bc93 X-Google-Attributes: gid1108a1,public X-Google-Thread: 103376,b87849933931bc93 X-Google-Attributes: gid103376,public From: davidb@datalytics.com (David Bradley) Subject: Re: What is wrong with OO ? Date: 1996/12/23 Message-ID: <32bf957f.492190732@news>#1/1 X-Deja-AN: 205599813 references: <32A4659D.347A@shef.ac.uk> <32A71BC6.2D857063@arscorp.com> <32A82AFE.255A@possibility.com> <58bq8c$3n6@news.utdallas.edu> <32ABCB1F.5207@possibility.com> <32b016d4.3487487@nntp.interaccess.com> <32B125E0.7880@calfp.co.uk> <32b55196.1250002@nntp.interaccess.com> <32B65D6C.6F10@deep.net> <32b7181e.2647652@news.nstn.ca> <599g39$l5v@gaia.ns.utk.edu> <32bb9c5b.166266748@news> <01bbee11$dcae8460$ca61e426@DCorbit.solutionsiq.com> content-type: text/plain; charset=us-ascii organization: Datalytics Inc. mime-version: 1.0 newsgroups: comp.lang.c++,comp.lang.smalltalk,comp.lang.eiffel,comp.lang.ada,comp.lnag.java,comp.object,comp.software-eng Date: 1996-12-23T00:00:00+00:00 List-Id: "Dann Corbit" wrote: >Think of an architect, designing a building. In the high level >drawing, they do not have a picture of every fastener and joint. >But somewhere, the detail will eventually be stored. True, but even at the high level there are annotations on the drawing that can not be caputured in images and are more than just comments. Thus I'd love a system where I can interact visually but be able to revert to a language when the need arose. >Back to the original subject, "What's wrong with OO?", there is >nothing wrong with Object Oriented programming. But it is not >the ultimate tool for each and every business problem. First, >you need to have an object model that fits the OO paradigm you >are using. Not all physical business problems can best be expressed >in this way (most of them can). Then you need to have someone >who knows OO techniques. There's the old lame joke about someone >who was having trouble with his chainsaw. He took it in to the >salesman to find out what the problem was. When the salesman started >it, he said, "What's that noise?" > >Know your tools. Quite true. I don't think anything is wrong OO. It's only failed for two reasons. One is lack of knowledge, the other is lack of proper design. People tend to forget that OO only makes programming easier for those who know how to use it. A poorly design OO system can be worse than a poorly design procedural system. Lack of good design results in a very brittle system. Alas no one seems to look beyond the short term. They don't want to make the investment upfront. "Just get it done". -------------------------------------------- David Bradley davidb@datalytics.com Software Engineer Datalytics, Inc. http://www.datalytics.com