Re: Disadvantages of Inheritance, Polymorphism and Encapsulation
From: topmind (topmind_at_technologist.com)
Date: 02/28/05
- Previous message: topmind: "Re: Application logic and Business logic"
- In reply to: tgbeck: "Re: Disadvantages of Inheritance, Polymorphism and Encapsulation"
- Next in thread: Jeff Brooks: "Re: Disadvantages of Inheritance, Polymorphism and Encapsulation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 27 Feb 2005 22:37:26 -0800
Why exactly is OO allegedly better for large projects? I find
procedural with a good RDBMS can better divide up "projects" into lots
of smaller projects because you work on mostly one task at a time and
use the DB as the primary messenging conduit. Thus, you mostly only
have to know the schema and a few project libraries and conventions. in
OO it seems one is faced with a mass sea of a million classes with no
easy way to know or navigate them. Reducing the message-passing to
queries of schemas is far more work-load divisable IMO.
OO seems to be a self-fulfilling prophecy in that it MAKES small
projects into big projects. Even Cobolers have figured out the
task-in-code-noun-in-DB division of labor and I have seen it work in
large city power utilities. (I'm not recommending Cobol here, BTW.)
-T-
oop.ismad.com
- Previous message: topmind: "Re: Application logic and Business logic"
- In reply to: tgbeck: "Re: Disadvantages of Inheritance, Polymorphism and Encapsulation"
- Next in thread: Jeff Brooks: "Re: Disadvantages of Inheritance, Polymorphism and Encapsulation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
