Path: utzoo!attcan2!uunet!seismo!sundc!pitstop!sun!hanami!landman From: landman%hanami@Sun.COM (Howard A. Landman) Newsgroups: comp.sys.mac Subject: Re: FullWrite Professional Keywords: Fullwrite memory Message-ID: <55034@sun.uucp> Date: 1 Jun 88 17:33:49 GMT References: <8805172016.AA09499@decwrl.dec.com> <53610@sun.uucp> <1713@pt.cs.cmu.edu> <537@aplcomm.UUCP> <416@esquire.UUCP> <2904@polyslo.UUCP> <418@esquire.UUCP> <2979@polyslo.UUCP> <807@eos.UUCP> Sender: news@sun.uucp Reply-To: landman@sun.UUCP (Howard A. Landman) Distribution: na Organization: Sun Microsystems, Mountain View Lines: 24 >In article <2979@polyslo.UUCP> dorourke@polyslo.UUCP (David O'Rourke) writes: >> You can use FWP on a standard machine. But are you saying that you should >>be able to everything a 2 meg or 2.5 meg Macintosh can do on a 1 meg Machine. In article <807@eos.UUCP> wiedmann@aurora.UUCP (Christian Wiedmann) writes: >Most definitely! I think one of the tenets of the Macintosh is configuration >independence. I don't think memory size should limit the things you can do, >just how fast they are done. >I can't think of any convincing reason to limit any user size because of >lack of memory. Such things should be hidden from the user. Why is it my >responsibility to adjust the chapter size when the program has much more >information about the problem, and could do it in such a way that I don't >have to worry about it? Gosh! Why should it be the program's responsibility when the operating system could do it in such a way that the program doesn't have to worry about it? This is known as virtual memory. It probably requires a hard disk, since you can't swap very much to an 800KB floppy :-). Of course, it would also require Apple to offer virtual memory capability ... Howard A. Landman landman@hanami.sun.com UUCP: sun!hanami!landman