Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site utastro.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!think!harvard!seismo!ut-sally!utastro!nather
From: nather@utastro.UUCP (Ed Nather)
Newsgroups: net.arch,net.lang.c,net.micro,net.micro.pc,net.micro.68k
Subject: Re: Re: Re: 286 vs. 68k
Message-ID: <208@utastro.UUCP>
Date: Fri, 7-Jun-85 11:28:56 EDT
Article-I.D.: utastro.208
Posted: Fri Jun  7 11:28:56 1985
Date-Received: Sun, 9-Jun-85 02:00:00 EDT
References: <675@dataio.UUCP> <2811@nsc.UUCP>
Organization: U. Texas, Astronomy, Austin, TX
Lines: 26
Xref: watmath net.arch:1345 net.lang.c:5358 net.micro:10710 net.micro.pc:4181 net.micro.68k:888

> In article <675@dataio.UUCP> bjorn@dataio.UUCP (Bjorn Benson) writes:
> >
> >I propose that we start a new newsgroup "net.micro.68vs286" so that
> >all you people who enjoy discussing benchmarks, registers, segments,
> >clock cycles and other marketing hype can do so away from the rest of
> >us.
> 
> I second the motion--only let's call it net.micro.compet.  I think that 
> there is a legitimate place on the net for discussion of the pros and cons
> of various architectures/implementations, and I think that the people who
> just want solid technical info about their specific micro/language ought
> to be able to read the appropriate newsgroup without having to wade through
> the competitive material.
> -- 
> Richard Mateosian

I thought that's what net.arch was for in the first place.  It's why I read it.
There is no better way to learn details of the "uglies" in a particular
architecture, and their consequences, than to read a debate by two competitors.
I say, let the flames roll on ...

-- 
Ed Nather
Astronony Dept, U of Texas @ Austin
{allegra,ihnp4}!{noao,ut-sally}!utastro!nather
nather%utastro.UTEXAS@ut-sally.ARPA