Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site ur-tut.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!whuxl!whuxlm!akgua!gatech!seismo!rochester!ur-tut!tuba
From: tuba@ur-tut.UUCP (Jon Krueger)
Newsgroups: net.micro,net.arch
Subject: Re: 386/68020 blather
Message-ID: <235@ur-tut.UUCP>
Date: Sun, 17-Nov-85 19:45:35 EST
Article-I.D.: ur-tut.235
Posted: Sun Nov 17 19:45:35 1985
Date-Received: Wed, 20-Nov-85 01:03:27 EST
References: <533@scirtp.UUCP> <2353@ukma.UUCP> <200@opus.UUCP> <421@ecn-pc.UUCP>
Reply-To: tuba@ur-tut.UUCP (Jon Krueger)
Organization: Univ. of Rochester Computing Center
Lines: 12
Xref: watmath net.micro:12740 net.arch:2110

>In almost all cases a 68020 or 386 will do the job fairly well in a given
>application. What really amazes me is that I NEVER hear any comments about
>the development environments.... You know, those things that really count
>in the order of the universe and the cost of a development program......

Well said, and it needed saying, too!

Although I read net.arch to get ideas on architectures and hardware that
implements them, when it's time to generate code I want tools, not marketing
hype.  Of course, if the architecture lasts a while, it will gradually
attract tools.  If the tools are good and available and cheap, I can enjoy
all the features of a truly superior architecture.