Intel may fight and win against this remediation, but they need to open their eyes: Java, .Net, Linux.... The x86 instruction set is slowly becoming irrelevant.
If Microsoft were to release Win7 for ARM tomorrow and put actual support for all sectors behind it, Intel stock would tumble.
What part of "Ph'nglui mglw'nafh Cthulhu R'lyeh wgah'nagl fhtagn" don't you understand?
How on earth do Java, .Net, or Linux make x86 irrelevant? You're comparing two different platforms with an entire operating system, and then comparing *that* to an architecture. Hopefully you realize that no modern processors actually execute x86 instructions--x86 instructions are broken into micro-ops (sometimes called uops) that are then executed.
Even the original "86" designation (meaning 8 registers, 16-bit processor) is long since obsolete--not only do we have 32-bit and 64-bit chips (obviously), Intel has used register-renaming to 'trick' architectures since the days of the Pentium Pro.
>> How on earth do Java, .Net, or Linux make x86 irrelevant?
Think about it:
Both Java, and .Net apps are compiled to Intermediate Languages. These distributed apps will run on any system with a Java VM or CLR implementation (and supporting libs). The JIT compilation will rewrite it to any architecture. I've written Gtk GUIs with Mono such that you can run the same .exe on x86-Windows or Cell-Linux... no changes necessary.
Linux will run on any system it's recompiled for. x86 instruction set or not. (Practically) All the apps are open-source and can be recompiled for the same new CPU.
These all destroy the dependence on the x86 instruction set for the purpose of running common apps. If history shows us anything, there will be even more abstraction from the hardware in the future. Intel's going to have to make money on the performance of their hardware, not artificial value of an instruction set.
Intel and Microsoft are trying the same trick: Lock everyone into your API - be it the Windows API or the x86 instruction set. Abstracting things up to higher levels is going to kill those two. MS knows this, or their supporting CLR framework library wouldn't be proprietary.
NEWS TIPS |
This site is intended for informational and entertainment purposes only. The contents are the views and opinion of the author and/or hisassociates. All products and trademarks are the property of their respective owners. All content and graphical elements areCopyright © 1999 - 2014 David Altavilla and HotHardware.com, LLC. All rights reserved. Privacy and Terms