Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!lll-winken!elroy.jpl.nasa.gov!sdd.hp.com!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!roundup.crhc.uiuc.edu!ux1.cso.uiuc.edu!news.iastate.edu!skank
From: skank@iastate.edu (Skank George L)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: How to improve Workbench 2.0!
Message-ID: <1991Jan29.234550.20638@news.iastate.edu>
Date: 29 Jan 91 23:45:50 GMT
References: <1991Jan27.105252.7019@marlin.jcu.edu.au> <1991Jan27.135843.2056@mintaka.lcs.mit.edu>
Sender: news@news.iastate.edu (USENET News System)
Organization: Iowa State University, Ames, IA
Lines: 45

In article <1991Jan27.135843.2056@mintaka.lcs.mit.edu> rjc@geech.ai.mit.edu (Ray Cromwell) writes:
>In article <1991Jan27.105252.7019@marlin.jcu.edu.au> glmwc@marlin.jcu.edu.au (Matt Crowd) writes:

>>6) DisplayBeep() Totally gross.  Change it fast.  There is already
>>a PD hack to do what it should do on a fish disk...
>
>  Personally, I like the flash better. I turn my sound down at night not to
>wake others up, and the flash is nice. Also, sticking sound samples
>in a DisplayBeep() routine slows the system down. If a BBS sends a bunch
>of CTRL-Gs it takes up to 30 secs sometimes to play all the queued 
>sound requests.

   Additionally, I wouldn't want large sound samples hanging around in chip
ram just so that the computer could beep (yawn, belch, fart, whatever).  I
also like the look of DisplayBeep().  If such a sound option were added,
to DisplayBeep() then there should also be an option to turn the sound off
and free up the resources.


>>26) The most major gripe is how easy it is to crash the system. 
>>Other systems are getting memory protection.  AmigaDOS needs it. 
>>At least provide a way for new programs written today to use 
>>memory protection and leave the old ones unprotected.  Eventually,
>>in about two years, most programs people run will be protected and
>>the old system can be phased out.
>
>  AmigaDOS as it is now will never have memory protection. AmigaDOS is
>fast because it uses shared memory. There is lots of old GOOD software
>that will not be updated, and thus unusable(maybe the company went under, or
>the author isn't support it anymore). Its just as easy to crash the
>Mac as it is with the Amiga if you have buggy software. What we need
>is bug free software. Even with memory protection, a bad program will
>crash, and you will lose your work. The rest of the system will
>remain intact, but you still lost what you were working on.

     This is a pet peeve of mine.  Memory protection is nice for developers
but IT IS NOT AN EXCUSE FOR WRITING POOR SOFTWARE!  A program that works, is
fully debugged, tests for insufficient memory conditions, frees its resources,
etc. does not need memory protection.
					--George
--

George L. Skank			|
skank@iastate.edu		|Fast cars, fast women, fast computers...
Senior, Electrical Engineering	|(not necessarily in that order)