Newsgroups: comp.sys.amiga.advocacy
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!menudo.uh.edu!lobster!sugar!peter
From: peter@sugar.hackercorp.com (Peter da Silva)
Subject: Re: 8-bit death
Message-ID: <1991May13.003426.259@sugar.hackercorp.com>
Organization: Sugar Land Unix -- Houston, TX
References: <1991May5.024025.19463@sugar.hackercorp.com> <1991May7.064810.905@kessner.denver.co.us> <1991May10.005049.8355@NCoast.ORG>
Date: Mon, 13 May 1991 00:34:26 GMT

In article <1991May10.005049.8355@NCoast.ORG> allbery@ncoast.ORG (Brandon S. Allbery KB8JRR/AA) writes:
> Peter, I fail to understand this.  Where does MacOS fall short?

Hi!

The MacOS fails in not having a scheduler, to manage CPU time in an efficient
and equitable manner. CPU time is another resource to be managed, and if the
system software doesn't do so (which it doesn't on the Mac: each application
is solely responsible for its use of CPU time and scheduling the next task to
run) then it's not managing all the major system resources:

	disk space
	memory
	stream I/O devices
	CPU

More recently, screen real estate is becoming an O/S resource... but not all
systems have manageable screen hardware. They all have CPUs.

The Mac system software has acceptable disk management, acceptbale memory
management, acceptable stream device management, and phenomenal screen
management. The system software, however, does not manage CPU time worth
a damn.
-- 
Peter da Silva.   `-_-'
<peter@sugar.hackercorp.com>.
