Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 UW 5/3/83; site uw-beaver
Path: utzoo!watmath!clyde!burl!ulysses!mhuxj!houxm!vax135!cornell!uw-beaver!info-mac
From: info-mac@uw-beaver (info-mac)
Newsgroups: fa.info-mac
Subject: Re: Why is the Mac so slow?
Message-ID: <2326@uw-beaver>
Date: Mon, 26-Nov-84 23:42:30 EST
Article-I.D.: uw-beave.2326
Posted: Mon Nov 26 23:42:30 1984
Date-Received: Wed, 28-Nov-84 03:56:11 EST
Sender: root@uw-beave
Organization: U of Washington Computer Science
Lines: 15

From: Michael Rubin <RUBIN@COLUMBIA-20.ARPA>
Nobody ever said that Apple was good at designing operating systems.
I've never figured out quite what the Mac spends its time doing when it
launches an application, but it is reading way too much information in
the wrong order.  This is an OS problem - nobody ever optimized the
Launch operation to minimize disk seeks (in fact it seems to have been
pessimized :-), which explains slow startup and shutdown (launching the
Finder again) of applications.

MacPascal is slow for another reason: it's an interpreter, not a compiler.
Everybody claims they can't fit a compiler into a 128K single-drive Mac,
though for years compilers have been written for machines with 16K to 64K
of memory and single-density 140K disks.  That's right, blame it on the
machine....
-------