Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83; site opus.UUCP Path: utzoo!watmath!clyde!burl!mgnetp!ihnp4!zehntel!hplabs!hao!cires!nbires!opus!rcd From: rcd@opus.UUCP (Dick Dunn) Newsgroups: net.news Subject: Re: nuking newsgroups (and memory constraints) Message-ID: <545@opus.UUCP> Date: Fri, 22-Jun-84 01:42:51 EDT Article-I.D.: opus.545 Posted: Fri Jun 22 01:42:51 1984 Date-Received: Fri, 22-Jun-84 05:16:05 EDT References: <1966@utcsstat.UUCP> Organization: NBI, Boulder Lines: 23 It's a little amazing to me that we're playing this game of "everybody has a VAX or 68000; why worry about 11's?" Does anyone realize that DEC has turned out a high-end 11-on-a-chip (or two or three) within the last year? That's point #1 - it ain't dead yet, by a long shot. Point #2: > So what ? Given any amount of memory, there will always be a > programmer out there to fill it up with an application that > used to run on half as much memory before, without any significant > improvements over anything. (Oh sure ! space vs. speed trade-off - > only if you knew what needs to run faster !!!) This was well-put, and it goes for ANY address space. If you don't believe it, you probably don't remember the story a few years back in a trade journal explaining how someplace had figured out a clever way to get around the 16-MEGAbyte address-space limitation per process that exists on a 370. That's right - someone not only blew out the top end of 16 Mb in one process; it hurt enough that they "solved" the problem. [Please don't bother to write to tell me that the 370 is most of the problem. You can divide the memory size by 2 or 4 and it's still absurd.] -- Dick Dunn {hao,ucbvax,allegra}!nbires!rcd (303)444-5710 x3086 ...Cerebus for dictator!