Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!sdcsvax!maiden
From: maiden@sdcsvax.UCSD.EDU (VLSI Layout Project)
Newsgroups: comp.sys.mac
Subject: Re: MPW system
Message-ID: <3824@sdcsvax.UCSD.EDU>
Date: Fri, 11-Sep-87 20:06:30 EDT
Article-I.D.: sdcsvax.3824
Posted: Fri Sep 11 20:06:30 1987
Date-Received: Sat, 12-Sep-87 20:28:25 EDT
References: <429@aucs.UUCP> <234@dbase.UUCP>
Reply-To: maiden@sdcsvax.UCSD.EDU (VLSI Layout Project)
Distribution: na
Organization: U.C. San Diego
Lines: 30

In article <429@aucs.UUCP>, paul@aucs.UUCP (Paul Steele) writes:
> Which is better: the MPW development system from APDA or Lighspeed Pascal
> and C from THINK.  I know MPW comes with 6 inches of documentation, but
> is there anything in it that isn't in Inside Mac.  Comments please.

I have used the Lightspeed C product for a 35,000 line project and Pascal
for a 15,000 line one.  No complaints except that Think should put in
some sort of revision control.  I have also used MPW Pascal, C, and alone,
but not for anything over 10,000 lines yet.

I have attempted group projects in Lightspeed C twice with astonishingly
poor results (astonishing in comparison to what a single user can do).
MPW shines in well-planned group projects (where good docs are a must).
However, MPW is *SLOW* and produces *MEDIOCRE* code.  MPW needs another
optimizer.

What it boils down to:
   Lightspeed C is optmized for single user programmers
      - fast turn-around
      - easy-to-use and friendly
      - some features replace good code documentation (global lookup, etc.)
   MPW is optimal for group projects and long-term control
      - shell scripting
      - potential revision management
      - useful utilities for source code control
      - good control for group coding

 Edward K. Y. Jung
 ------------------------------------------------------------------------
 UUCP: {seismo|decwrl}!sdcsvax!maiden     ARPA: maiden@sdcsvax.ucsd.edu