SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Intel Corporation (INTC)
INTC 36.78+2.7%Nov 26 3:59 PM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: puborectalis who wrote (66995)10/18/1998 10:58:00 PM
From: Paul Engel  Read Replies (3) of 186894
 
Stephen - Re: NSM/Cyrix, IDT and AMD.

NSM is wounded - maybe mortally. They haven's had a competitive part in over 18 months.

IDTi is completely uncompetitive - they are the walking dead.

AMD has to keep dropping their prices as Intel introduces newer, faster processors and cuts the prices on its existing ones.

This leaves AMD in a war of attrition with Intel.

If Intel's Katmai instructions become the industry favorite for enhanced video, 3D, rendering and voice-recognition software developers, AMD will be caught with incompatible CPUs that will have to be FURTHER discounted to essentially unprofitable levels.

And, AMD's K7 - the "FUTURE" of AMD, requires a totally NEW mechanical and electrical interface - different from anything currently existing in the x86 world.

The K-7 will have to offer twice the performance of an Intel CPU at half the price just to be CONSIDERED by a customer.

Remember - the K-7 is a SOLE SOURCE PART and with AMD's history, what reputable server or workstation manufacturer will commit to a SOLE-SOURCED device - made in just one AMD wafer fab?

Intel on the other hand has MULTIPLE wafer fabs producing their parts, providing virtual multiple-sourced CPUs - and will continue to do so, giving their customers an extra margin of safety when it comes to CPU availability and delivery.

Paul
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext