What IT Should Know About Windows 8
In the two weeks since Microsoft unveiled its Windows 8 Developer Preview at Build, more than a million people have downloaded the bits, leaving the vast majority of IT pros wondering what in the world their organizations may someday be getting into.
Here, Microsoft has been characteristically mum, except for the targeted and highly vetted postings of the Windows engineering team on its Building Windows 8 blog. That dearth of substantial information, not to mention reams of unanswered questions, has not prevented Preview users from providing meaningful observations on Windows 8 for the end-user's perspective.
[ See InfoWorld's Windows 8 preview visual tour. | Galen Gruman outlines how Microsoft may finally be making Windows winners. | Keep up to speed on the key Microsoft news and insights with InfoWorld's Technology: Microsoft newsletter. Sign up today! ]
But getting an understanding of the client-side nitty-gritty in the corporate world is no easy matter, especially when looking at pre-release code. Microsoft is not answering questions, and Windows 8 is no doubt a year away, meaning that nothing is set in concrete. But even with the usual pre-beta admonitions, from an IT and developer perspective there's still a lot to chew on -- most notably, how Windows 8's bifurcated interface and support for both Intel and ARM signal tough choices ahead for supporting corporate end-users in the post-PC era.
Shift in Surface, Change in Architecture Support
The first major change introduced in Windows 8 is its bifurcated interface. Terminology varies, but I'll call one interface "Metro," to refer to the UI with the tiles (see Figure 1), and the other "Desktop," because it looks and acts much like the Windows 7 desktop, except for the black hole in the lower-left corner. (For a more extensive look at Metro, see InfoWorld's Windows 8 Metro visual tour.)
Figure 1: The tiled Metro interface. When you install an application in the Desktop interface, in some cases Windows places a tile that runs the Desktop application in the Metro interface (c.f., the Google Chrome tile).
The other major factor for Windows 8 is that it is designed to run on both Intel/AMD hardware and the newer ARM-based offerings. Intel tablets coming out in the near term will be comparatively heavy, and the batteries won't last as long. ARM tablets will likely be lighter, longer-lived, and probably cheaper. Some day, Intel will catch up. But for the near future, at least, the most popular tablets will be based on ARM architectures.
If you've watched the demos and keynotes and read the glib reports, you may be under the impression that Microsoft has created one operating system that works on desktops, laptops, and both Intel and ARM tablets -- "Intel and ARM, not Intel or ARM," to quote Microsoft CEO Steve Ballmer. While that may be literally true, at least in a marketing sense, the devil is in the details, and we're beginning to see some gnarly problems that result from mixing architectures and OSes -- especially issues that corporate developers and IT departments will encounter.
The Three Faces of Windows 8
Instead of looking at Windows 8 as a unified operating system running on two different sets of hardware -- along the lines of, say, Windows NT, which ran on several different platforms -- IT and developers should think of Windows 8 as having three distinct flavors, shown in Figure 2.
Figure 2: The three very different faces of Windows 8, from a corporate developer's perspective.
Based on the Developer Preview, it's very likely that Microsoft will maintain near-100 percent compatibility with Windows 7 apps, running on the Windows 8 Desktop with Intel/AMD hardware. All of the development tools IT uses with Windows 7, including Silverlight, should work with Windows 8, unchanged, as long as the target is the Windows 8 Desktop on Intel/AMD hardware.
But if you're aiming for the Desktop on ARM machines, it's a completely different can of worms. There's a reason why the tablets given away at the Build conference were Intel-based.
If you keep those three different scenarios in mind (Metro vs. Desktop on Intel vs. Desktop on ARM), Microsoft's official box chart, describing the highest-level interactions in Windows 8, makes some sense. (See Figure 3.)
Figure 3: The way Windows 8 hangs together, from Ales Holecek's presentation at Build, approximately 8:30 into the demo.
Now you see the flip side of Steve Sinofsky's statement during last week's financial analyst Q&A session: "We've been very clear ... that the ARM product won't run any X86 applications. What we announced yesterday for the first time was that when you write a Metro-style application, all the tools are there to enable you in any of the languages that we support to automatically support ARM or X86."
Next Page: Developers' concerns...