Intel: No x86 Compatibility on ARM Version of Windows 8
Linked by Thom Holwerda on Wed 18th May 2011 21:50 UTC, submitted by fran
Windows The ARM version of Windows 8 might have just become the most desired version of Windows in our hearts and minds. After us talking about legacy code and backwards compatibility in Windows for years now, an Intel senior vice president, Renee James, has just stated that Windows 8 on ARM will not have any form of compatibility for legacy applications whatsoever. Update: Microsoft has responded to Intel's claims. "Intel's statements during yesterday's Intel Investor Meeting about Microsoft's plans for the next version of Windows were factually inaccurate and unfortunately misleading," the company said, "From the first demonstrations of Windows on SoC, we have been clear about our goals and have emphasized that we are at the technology demonstration stage. As such, we have no further details or information at this time."
E-mail Print r 1   · Read More · 74 Comment(s) http://osne.ws/j3q
Thread beginning with comment 473692
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: It makes sense
by werpu on Thu 19th May 2011 07:57 UTC in reply to "RE[5]: It makes sense"
werpu
Member since:
2006-01-18

"Sure they can rewrite all major apps in .NET. I don't think it would be harder to implement Office or IE in .NET than is to implement Visual Studio 2010.


IRIC, only parts of VS 2010 were converted over to .NET, such as the code editor. I don't think they rewrote the compilers and the entire UI. "
You simply cannot unless you want to run into serious speed hits. .Net probably has less of a problem from a UI standpoint because they can hook natively into the Windows controls. But as soon as you write custom controls expect some speed hits. Bearable but you have them. Entire IDEs have been written entirely in java and people can work with them quite well, I am one of those who uses Java tools day in day out, but you cannot neglegt the fact that the underlying vm takes its toll to some degree. The same goes for .Net which has a similar performance.

Reply Parent Score: 2

RE[7]: It makes sense
by tanzam75 on Thu 19th May 2011 16:02 in reply to "RE[6]: It makes sense"
tanzam75 Member since:
2011-05-19

Only Winforms hooks into the Windows native UI.

The Visual Studio 2010 editor uses WPF, which manages and draws the entire UI itself. At the bottom layer, of course, it goes into DirectX and hits native code. But everything above that is managed. All the built-in controls, from buttons to scrollbars -- all written in C#.

Reply Parent Score: 1