From: rdd@cactus.org (Robert Dorsett)
Subject: Re: What should Apple do to the Mac to make it better for games?
Organization: Capital Area Central Texas UNIX Society, Austin, Tx
Date: Thu, 31 Dec 1992 07:07:43 GMT

In article <1htqadINNe5g@usenet.INS.CWRU.Edu> an780@cleveland.Freenet.Edu (Travis Grundke) writes:
>
> Okay, since the arguments over sprits, slow games, etc. seems to have
>taken a big presence here lately <grin>, what SHOULD Apple do in its next
>batch of Macintoshes (dream dream dream, dream a little dream) to make the
>Macintosh "More adept" to running games?  
> [...]
>some things which I've learned and picked up seem to be that Apple should
>ideally implement a GRAPHICS BLITTER co-processor.
> [...]
>This frees up
>the CPU to handle other calls from the program such as I/O and basic frame
>direction. It also is great for when you've got lots of video on screen
>and/or animation.
>
> Any other ideas from others out there?

Let's get away from slang-jargon in discussing this stuff, to start with.

Let's also get away from discussing "games."  Apple doesn't like games.
Apple doesn't support games.  We're never going to get Apple to up the
performance just because we want to play games.  There are other activities--
namely, computer-assisted instruction/training, which can make pretty similar
demands: the PC completely dominates this arena at any appreciable level.
CAI is in its infancy: we will start to see a LOT more simulation and
processor-intensive activities, over the coming years, less straightforward
rote drilling.


So, to support CAI, I think we should see, at a MINIMUM: 

1.  Parallel graphics architecture, user-extensible.  Ideally, even, an
OS that uses its own processor, reserving a "working" processor for program
execution only.  

2.  Memory protection.  This affects everyone.  IT IS OUTRAGEOUS that the
Macintosh still has a cooperative operating system: especially in a networked
envionment.  A single bug in a single program can take down the entire OS:
we need memory protection, offering a standardized program space to each
application.  If the application dies, it dies in its own turf, not being
able to corrupt the data or processes in other application spaces.

This is particularly important for "CAI," since such developers are often 
start-ups, lower on the OS learning curve, and more likely to make
mistakes.  They'll learn from their installed user base: that user base 
shouldn't be put at risk.

I think there are also real liability issues in not offering protected memory.
If the Mac would offer this, it'd be a major jump over anything the 
competition has to offer.  As a developer, if the competition starts offering
memory protection, I'll probably switch my platform emphasis.

3.  For games, simulations, CAI, applications, whatever: kill the
damned 12" display.  Offer trade-in rebates: get everyone to at least 
640x480.  Reduced resolution was the stupidest thing Apple's done in recent
memory.

4.  Lastly, games only: improved luminosity on display devices, preferably
programmer-selectable.  If one animates a lightbulb, it'd be nice if it 
GLOWED, not just be an "earthtone" blue.  



---
Robert Dorsett
rdd@cactus.org
...cs.utexas.edu!cactus.org!rdd