Windows 8 will run on ARM processors – a natural home for Silverlight?

Microsoft announced today at CES in Las Vegas that the next version of Windows will run on ARM as well as Intel CPUs. But why? The reason is that ARM CPUs have huge momentum in mobile computing, thanks to their low power consumption. Microsoft wants Windows to support System on a Chip (SoC) architectures such as NVIDIA’s Tegra 2, which has two ARM Cortex-A9 CPUs combined with an HD-capable graphics processor in a single package. In its press release, the company is careful not to upset established x86/x64 partners Intel and AMD too much, emphasising that Windows will run on SoC packages based on those CPUs as well.

It is an interesting announcement, but one that raises as many questions as answers. The first concerns Microsoft’s mobile strategy, with Windows now seeming to encroach on territory that you have thought belonged to its embedded operating system, Windows CE, which underlies both Windows Mobile and Windows Phone 7. With all its legacy APIs, full-blown Windows does not seem ideal for low-powered, resource-constrained mobile devices; yet the company seems set on bringing full Windows rather than something based on Windows Phone 7 to the emerging tablet market.

The second issue is that applications will need at least re-compiling, and in many cases some re-coding, in order to run on ARM CPUs. Microsoft says it will deliver Office for ARM:

Sinofsky: Microsoft Office is an important part of customers’ PC experience and ensuring it runs natively on ARM is a natural extension of our Windows commitment to SoC architectures.

Windows and Office alone is enough for a decent business device; but customers who buy Windows on ARM expecting their existing games or applications to run will be disappointed.

We have been here before. In the early days of Windows CE, devices ran a variety of processors such as MIPS or Hitachi SH3, and developers had to compile multiple binaries and create setups that installed the right one on each device. In an attempt to overcome the friction this created, Microsoft introduced the Common Executable Format (CEF) with Windows CE 3.0 in 2000. This was an intermediate language format which was translated to native code by a “translator” when it was installed onto a device.

It sounds  a bit like .NET or Java; and it was indeed a forerunner of the .NET Common Language Runtime, which appeared in 2002. However, CEF never really caught on. Although it solved deployment issues, it introduced performance problems and was troublesome to debug. Most developers preferred to stick with true native code.

Today though .NET is mature; and we also have Silverlight, a cross-platform implementation of the .NET Framework combined with multimedia player and graphics framework. If Microsoft includes .NET and Silverlight in its ARM build of Windows, that would solve some of the deployment problems, especially for business devices. Many custom applications are built for .NET; and these would in principle run without any need to recompile, since a .NET executable is intermediate code which is compiled to native code at runtime, though any code which includes “platform invoke” calls to native APIs would not work.

It is surprising therefore that neither .NET nor Silverlight is mentioned in Windows president Steve Sinofsky’s Q&A about Windows on ARM. Still, we should not read too much into that. It would be madness if Microsoft did not support its .NET technologies on this new platform, would it not?

4 thoughts on “Windows 8 will run on ARM processors – a natural home for Silverlight?”

  1. I’ve been thinking along similar lines – I think that there’s a possibility that a future version of Windows Phone will be built upon the core of Windows 8. That might be partly why unmanaged code isn’t accessible for all developers at the moment – if the majority of application are pure managed code, then in theory they should “just run” on a new runtime (as long as the framework supports the same APIs!)

  2. Of course, Tim, when people build their businesses and code bases around proprietary Microsoft technology, they’ve incurred a HUGE liability. MS will drop them in a New York minute the instant that their clever analysts determine that they’ll make more profit (or hold onto their monopolies more effectively) by doing so. Loyalty to customers and developers is not part of their DNA. Just saying.

  3. @Dave: stop spreading FUD. Any idiot can figure out what drives Microsoft; doing the same for a company not compelled by profit is a lot harder. Microsoft is beholden to developers, not disloyal to them.

    Why is it that anything invented by Microsoft is proprietary and, therefore, bad, but when Apple/Google/Sun does it, no one calls it a liability?

  4. The hard part about porting .NET would be porting the JIT compiler, and .NET without the JIT would not make sense. Not that I disagree with the thrust of the article, but porting a JIT to a new processor architecture is a lot of work.

Comments are closed.