Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!sdd.hp.com!caen!sol.ctr.columbia.edu!emory!gatech!usenet.ins.cwru.edu!ncoast!davewt
From: davewt@NCoast.ORG (David Wright)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: NeXT-bashing party (hit "n" if you're not interested :-))
Message-ID: <1991Apr2.025639.10675@NCoast.ORG>
Date: 2 Apr 91 02:56:39 GMT
References: <15L002.N06Qt01@JUTS.ccc.amdahl.com> <1991Mar26.043648.17656@NCoast.ORG> <4aQk02L406l501@JUTS.ccc.amdahl.com>
Organization: North Coast Public Access Un*x (ncoast)
Lines: 58

In article <4aQk02L406l501@JUTS.ccc.amdahl.com> kls30@DUTS.ccc.amdahl.com (Kent L. Shephard) writes:
>
>Not that easy.  More pins on a '040 some of those pins are power pins.
	I clearly said "in the CPU slot". The number of pins on the '040 is
irrelevant. All signal lines are provided for on the CPU slot, and I would be
VERY suprised if it needed any power lines with different levels than the '030
(or ANY modern CPU).
>The '040 doesn't have the full 68882 built into it.  This means that
>either you have to trap the instructions and provide emulation via the OS
>or you can recompile all your applications.  The '040 is NOT just a drop
>in replacement for an '030.
	Absolutely you would need some software support for the '040 to use
the full functionality of the FP routines. This has zero to do with the
physical aspects of designing an '040 board to fit the CPU slot of the 3000.
This is strictly a software issue. And if I am not mistaken, the routines that
are not included in the '040 are the less used functions, and again, if I am
not mistaken, AmigaDOS 2.0 *DOES* provide for them in the standard math
libraries (you know, the ones that will allow your program to run with
no FPU, a '881, or a '882 with no coding changes). Personally, as I NEVER use
FP, and I probobly own no program that does use FP and does make use of the
seldom used missing functions, and I am pretty sure of #2 above, I consider this
a moot point. And again, it's a software question, not a hardware one.
>You use interface builder.  You don't write code for buttons, sliders,etc.
>You write your application in plain old C and your application talks to
>button and slider objects.
	Gee, you mean just like in AmigaDOS 2.0? Boy, all this time I have
been using PowerWindows and various other PD programs to create
ready-to-compile modules that I just link in with "plain old C" modules I
must have been doing some extra step somewhere.
>>I know NOBODY who fits all three of these, and very few who know 1 want to
>>do 2 or 3. (Like working on Intel machines)
>            ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>I happen to like Intel machines for some applications.  Engineering
>software.  It's cheaper than any other platform, more polished and more
>abundant.
	The 80x86 is more polished than the 680x0? This is a first I have
heard from someone who has used both. Most people who have worked with Intel
chips have been able to notice that the '[234]86 is just a hacked up and
souped up 808[0586], with the primitive early 70's segmentation
archetecture.
>>       Of course he did. For all of them in one way or another. If not
>Since yoou have no proof this is speculation.
	No, since I simply can't remember who wrote the article that appeared
a while back stating openly how much NeXT, Inc. payed Lotus to write it on the
NeXT, along with other "incentives" that would certainly sway any company
(free machines to use to develop it, etc.)
>
>>in cash on some, then by simply having his name on the NeXT company letterhead.
>>                                       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>This is called influence, NOT payment.
	Hmm, So if Bo Jackson puts his name on something it isn't going to
increase the sales and/or prestige of the products that manufacturer makes,
even if they are unrelated to the one he actually endorses? Take a marketing
class. When a well-known person has something to do with a product, people
remember the COMPANY who produces the product, NOT just the individual
product they saw him/her hold in their hands.

			Dave