Path: utzoo!attcan!uunet!garfield!john13
From: john13@garfield.MUN.EDU (John Russell)
Newsgroups: comp.software-eng
Subject: What's a PC? (was Re: Cynic's Guide to SE #6: Forthcoming)
Message-ID: <4935@garfield.MUN.EDU>
Date: 15 Oct 88 23:15:07 GMT
References: <9@helens.stanford.edu> <39400002@m.cs.uiuc.edu>
Reply-To: john13@garfield.UUCP (John Russell)
Organization: Memorial University of Newfoundland
Lines: 28

In article <39400002@m.cs.uiuc.edu> wsmith@m.cs.uiuc.edu writes:
]
]>A good rule of thumb I've observed is that anytime a project can
]>be done by one or (maybe) two people, a PC is probably your best choice.

]I don't
]have much respect for PC make facilities especially since a PC has limited
]concurrent execution powers to allow for the nested makes needed for the nested
]directory structure.

That isn't necessarily true of all PC's (personal computers, as opposed to
"IBM PC" which is what most people consider PC to mean).

An Amiga has concurrent execution powers limited only by available memory. You
might be able to fill up available memory, although it's no problem to make
heavily used executables resident (ie only one copy of executable code for
multiple invocations).

I've been disappointed with mainframe performance ever since the end of the
summer, when the load average went back to real-world levels and my compiles
started turning into meal-breaks :-(.

John
-- 
"The 68000 processor can't possibly handle a colour display. You must have a
 68020 system and not know it."
		-- Amiga and Atari ST owners shared a chuckle over this view
		   from sales *and* technical people at the local Apple dealer