Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!jarthur!nntp-server.caltech.edu!tybalt.caltech.edu!toddpw From: toddpw@tybalt.caltech.edu (Todd P. Whitesel) Newsgroups: comp.sys.apple2 Subject: Re: APW 2.0 Message-ID: <1990Oct10.030221.11913@nntp-server.caltech.edu> Date: 10 Oct 90 03:02:21 GMT References: <7666@darkstar.ucsc.edu> Sender: news@nntp-server.caltech.edu Distribution: comp.sys.apple Organization: California Institute of Technology, Pasadena Lines: 20 Nntp-Posting-Host: tybalt.caltech.edu unknown@ucscb.UCSC.EDU (The Unknown User) writes: > They now recommend people get/use Orca/C > From what I understand, APW C is basically an all text oooooold >version of ORCA/C.. Isn't that right? ByteWorks wrote APW C and sold it >to Apple and then they just updated it a lot into their own ORCA/C... Yep. Apple found that too much the APW code was owned by byteworks, meaning that many of the modifications they wanted to make would have to put up with stupid legal delays, whereas MPW (which was originally a conceptual ripoff of APW but is now a very respectable development environment) development could proceed full speed ahead since everyone working on it was in-house. Apple has given up trying to make APW reasonable and they now advocate either MPW IIGS or ORCA for GS application development. Todd Whitesel toddpw @ tybalt.caltech.edu