Newsgroups: comp.sys.amiga.advocacy
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!mintaka!geech.gnu.ai.mit.edu!rjc
From: rjc@geech.gnu.ai.mit.edu (Ray Cromwell)
Subject: Re: The Amiga's Future
Message-ID: <1991Jun4.231426.26126@mintaka.lcs.mit.edu>
Sender: news@mintaka.lcs.mit.edu
Organization: The Internet
References: <1991Jun4.003619.3661@news.iastate.edu> <1991Jun4.025024.823@mintaka.lcs.mit.edu> <49969@ut-emx.uucp>
Date: Tue, 4 Jun 91 23:14:26 GMT
Lines: 45

In article <49969@ut-emx.uucp> awessels@ccwf.cc.utexas.edu (Allen Wessels) writes:
>In article <1991Jun4.025024.823@mintaka.lcs.mit.edu> rjc@geech.gnu.ai.mit.edu (Ray Cromwell) writes:
>
>>  BTW, I think System 7.0 is a big failure/joke. It is incredibly slow
>>on anything less than an 030 with lots of ram. I've been reading
>>many accounts of users running even a simple application with a clock
>>program in the background and having the system become incredibly 
>>jerky and slow. One user in comp.sys.mac.system accounts of running
>>tetris and "superclock" resulting in the game becoming really sluggish
>>(on an LC). This  is pathetic, I can run multiple copies of tetris on
>>my A500 with a term program, and a clock and all of them run at near
>>full speed.
>
>I think you don't know what you are talking about.  7.0 runs just fine on
>a Mac Plus with 2 meg.  (Well, I guess "lots" wrt memory is relative.)
>
>I love this.  On the basis of ONE report about problems with 2 OTHER programs
>you have decide that System 7.0 is to blame.  You oughta go into tech support,
>where you'd be a god.
>
>At what bit depth was the LC running?  Was it running any other inits?  Was
>your A500 running a graphic shell?  Was it running an outline font display?
>
>Maybe you just know your A500 better than most Mac users know their machines.

  Maybe you should learn about programming first. I happen to know the A500
very well. What has it got to do with the fact that the Amiga handles
multitasking better than the mac? Outline font technology has little to do
with it unless Apple's implementation is brain damage. You only have to
compute an outline font when a program needs a new metric, and even 
then a caching mechanism would help out nicely. For outline fonts to
_continually_ bring down system performance, the implementation
would have to do something stupid like waste lots of CPU cycles between
each CHARACTER printed (e.g. calculate the character each time it is
printed rather than calculate a large area of the font and cache it)

  I know several people who are no longer running system 7 and have
switched back to 6.0.x because it was incredibly slow on their machine, sucked
up huge amounts of memory, and didn't work with several popular programs.

--
/ INET:rjc@gnu.ai.mit.edu     *   // The opinions expressed here do not      \
| INET:r_cromwe@upr2.clu.net  | \X/  in any way reflect the views of my self.|
\ UUCP:uunet!tnc!m0023        *                                              /