Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!gate.oxy.edu!oxy.edu!schorsch
From: schorsch@oxy.edu
Newsgroups: comp.sys.mac.programmer
Subject: Re: OOP--What do you think?
Message-ID: <712@gate.oxy.edu>
Date: 11 Apr 91 22:21:29 GMT
References: <1991Apr10.210516.25812@rice.edu>
Sender: usenet@gate.oxy.edu
Organization: Occidental College
Lines: 37

In article <1991Apr10.210516.25812@rice.edu> koops@elf.rice.edu (Ryan Richard
Koopmans) writes:
>I recently purchased THINK C 4.0.  When I looked at their
>object oriented implementation of the Mac interface, I was
>more than a little bit confused.  I've written lots of Mac
>applications before, and I'm comfortable with the traditional
>procedural kind of Mac programming.
>
>What I want to know is, is OOP the wave of the future in
>programming or just a passing fad?  Is it worth learning
>a new way of programming just to use the TCL?
>
>Maybe I'm just old fashioned, but I like the straight procedural
>way.  In all the message passing and things, I feel that the
>programmer gets too far away from the machine and works on a
>too abstract level.
>
>What do you think?
>

I also am wondering this.

I have heard that OOP produces mush larger code (4 times or more!!)
If this is so, since I am a perfectionist, I would prefer to spend the extra
time using procedural techniques to write smaller, faster code than to save
time and create a "clunky-slow" application. I can't help but to wonder if OOP
and not increased funtionality is the cause of the huge size of many recent
professional applications.(4-8 Meg for one app!?!?)

What do people think?

-Brent

                              !  "He was strangely relieved about 
Brent Schorsch                !   getting rid of his old fridge and
schorsch@oxy.edu              !   looked forward to enjoying a new phase
                              !   of fridge ownership" -Douglas Adams