Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!psuvax1!news From: melling@cs.psu.edu (Michael D Mellinger) Newsgroups: comp.sys.amiga.advocacy Subject: Re: NeXT/Amiga Flamage: Get a life. Message-ID: Date: 8 Apr 91 21:37:23 GMT References: <10834@uwm.edu> <46833@ut-emx.uucp> <46867@ut-emx.uucp> Sender: news@cs.psu.edu (Usenet) Organization: Penn State Computer Science Lines: 35 In-Reply-To: greg@ccwf.cc.utexas.edu's message of 8 Apr 91 18:42:16 GMT Nntp-Posting-Host: sunws5.sys.cs.psu.edu In article <46867@ut-emx.uucp> greg@ccwf.cc.utexas.edu (Greg Harp) writes: Please look up the definition of the word 'acceptable' before you use it again, then. BTW, with an 040 you should be able to pull off real-time animation in a window -- but of course you have the overhead of DP on the NeXT so you couldn't do it on _that_ platform. Damn shame... The overhead to the GUI isn't because of DP. The slowness that you get, if you get it, is because of paging. Virtual Memory. Need I explain further? >How much does the faster GUI improve your productivity? Personally, I >use the Unix shell and Emacs for a lot of my work. I'd say it improves my productivity quite a hell of a lot, actually. I commonly have several windows open, and several screens too. Given the amount of flipping/moving of windows and screens I do it'd be a real pain in the ass if a bunch of CPU was getting eaten up by a slow GUI. When compiling you don't want half of the CPU used in printing out compiler status messages, do you? I some how doubt that if half of the CPU is spent printing out compiler error messages when you compile a program. BTW, since you use the shell and Emacs so much I guess DP is just extra baggage, eh? It'd sure be nice if you could specify what windows were and weren't DP, wouldn't it? Forcing DP on the user was one of NeXT's many blunders. When was the last time that you used a NeXT? The speed of Display Postscript isn't a problem, and it does allow for more functionality. >-Mike