Building Windows for the ARM processor architecture
blogs.msdn.com
blogs.msdn.com
Style-wise, as often when reading MS 'blog posts', I wonder how many marketeers were in the committee writing it. This post is way longer than its content deserves, with repeated almost content-free adjectives such as "unique" or "intrinsic". To make things worse, it seems to suffer from serious copy-paste errors (for examples, search for "has a very high degree of commonality" or "enables creativity").
The post also sometimes almost conflicts with itself due to what I imagine to be marketing forces. For example: "WOA builds on the foundation of Windows" vs "With WOA you can look forward to integrated, end-to-end products—hardware, firmware and WOA software, all built from the ground up"
I also found it funny to read "of what we call, for the purposes of this post, Windows on ARM, or WOA". Are they really thinking that will prevent people from calling it WOA elsewhere? In a similar vein, we have "Note: This is not a product plan or even a hint at a product." and "(which are not the subject of this post)" Phrases like that belong in a press release, not in a blog post.
As a final reason why I do not like the writing style, I had to laugh when, over 1300 words in the article, I find "This post is organized with the following sections"
I'm still trying to wrap my head around this one... why would they limit the OS, instead of saying that Metro was it, and have the Office15 team build out Metro versions of their applications?
Having the desktop/classic mode be only for built-in utilities and Office seems, at best, extremely short sighted.
[1] http://allthingsd.com/20120209/windows-on-arm-complete-with-...
Plus, by keeping all the desktop utilities like Explorer and Control Panel as desktop apps in WOA it reduces the amount of work that needs to be done. When Windows 8 is being used on a desktop PC you'll want those to still be desktop apps, and they probably won't be used enough on a tablet to justify rewriting them all as Metro applets.
- Internet Explorer 10
- Office 15 (Word, Excel, PowerPoint, OneNote). What about Outlook, Visio, etc.?
- Windows Explorer
- Wordpad? Solitaire? Remote Desktop Client?
And that's it.
If I want to, say, unrar or un-7z a file I just downloaded, I'll need to go back to a Metro 7z app to do that?
Or what if I want to use Chrome or Firefox? Does this even comply with Microsoft's EU obligations (the browser ballot, etc.)?
Leaving the desktop environment only available to Microsoft apps is a very slippery slope, and I think it'll be a serious point of contention for developers and users. It really has to be all-or-nothing.
I have a feeling that if Win8/ARM takes off, this could be a big market -- maybe I should take it a bit more seriously.
>Windows on ARM software will not be sold or distributed independent of a new WOA PC
I don't want to have to buy a new tablet with the same hardware just to run a new OS. Hopefully Technet subscribers can get a copy, or XDA et al can manage to provide. It'd be nice to have a legal option, though.
For instance, Atom support was lost somewhere along the official way, but third-party patched kernels exist to reintroduce it (c.f. Nawcom et al).
And will they actually let you sell an application through the Windows Store whose purpose is to run other non-Window-Store-acquired code? It seems likely that they'll have to institute a policy against such applications, just like the Apple App Store, to prevent end-runs around the Windows Store.
and
"We architected our approach to ensure that software and peripherals can all benefit from the diversity enabled by the ARM architecture, along with the choice of form factors and manufacturers, and the openness of the platform."
seem to be in conflict. How is my being unable to install an OS a good thing? These comments (along with later mention of UEFI and some other things) cause me some discomfort.
Well, looks like Apple won the hearts and minds of consumers--we now are looking at a future with much greater integration of software and hardware and much less freedom. Thanks folks.
EDIT: To clear up potential confusion, I'm not saying that what Apple did was not good business or that their success was totally bad--I merely am pointing out that the tight UX pushed by that company (and then aped to varying degrees by others) has out of necessity driven things in this direction.
EDIT2: "In fact, WOA only supports running code that has been distributed through Windows Update along with the full spectrum of Windows Store applications." Oh goody.
http://arstechnica.com/business/news/2012/01/microsoft-manda...
Where something sits on several axes of flexibility is certainly interesting and can be cause for concern, but let's lose the nonsense disproved by real software.
There are a few, and we could probably enumerate them all right here. The reason they stand out is that almost no one does that, and that it's not an effective development environment for most people.
Personally, I'd sooner shift careers to road mending than try to program on an iPad.
And, personally, I'd love to be able to run Xcode on an iPad. With a Bluetooth keyboard it would be practically identical to the laptop I use now, but better for my back and wrists.
In fact, WOA only supports running code that has been distributed through Windows Update along with the full spectrum of Windows Store applications.
WOA PCs will be serviced only through Windows or Microsoft Update, and consumer apps will only come from the Windows Store, so you never have to worry if a program will run because you are not downloading or installing from a DVD outside of the store experience. A WOA PC will feel like a consumer electronics device in terms of how it is used and managed.
Ergo, they probably won't be working hard to lock the platform from other applications (what little applications that will exist, that is)