A new version of the Windows 8 operating system could shut out browsers such as Firefox and Chrome, according to Mozilla. Microsoft has been saying all along that x86 apps wouldn't run on Windows on ARM and it explicitly said there would be no third-party code on Windows RT when it announced the details of the platform back in February.

That's no plugins for IE on the Windows RT desktop as well as no desktop Firefox and Chrome. According to Mozilla, the makers of Firefox, Microsoft is planning to allow only one fully-functioning browser on Windows RT: Microsoft's own Internet Explorer. Writing on the Mozilla blog, Harvey Anderson, general counsel for the company, lashed out at Microsoft for the slight, and called the alleged move "an unwelcome return to the digital dark ages where users and developers didn’t have browser choices."

see here.This only applies to the tablet/smartphone/whatever version of windows, where applications must be programmed using a specific language which is not what firefox is coded in. It's a situation not unlike what happens in android/ios, I'm not surprised. I would be worried if this were to happen on the "regular" desktop Windows.

This only applies to the tablet/smartphone/whatever version of windows, where applications must be programmed using a specific language which is not what firefox is coded in. It's a situation not unlike what happens in android/ios, I'm not surprised. I would be worried if this were to happen on the "regular" desktop Windows.

+1 - I can't use FF on my current Windows 7 phone either ... So what exactly is "changing"? Sounds like chapter two of the Vista era FUD bashing fad is cranking up to me.

I love the way the teaser headline contradicts the article, extremely typical these days. In the future there will be no articles, only teaser headlines. That's the only part people remember when they retell the story anyway (present company excepted, of course).

A more accurate headline would be "There's still not an ARM version of Firefox, if anyone cares"

This only applies to the tablet/smartphone/whatever version of windows, where applications must be programmed using a specific language which is not what firefox is coded in. It's a situation not unlike what happens in android/ios, I'm not surprised. I would be worried if this were to happen on the "regular" desktop Windows.

+1 - I can't use FF on my current Windows 7 phone either ... So what exactly is "changing"? Sounds like chapter two of the Vista era FUD bashing fad is cranking up to me.

What a stupid article - Firefox and Chrome will run just fine on Windows 8 on a PC, laptop or x86 tablet (so long as you have access to the desktop).

It is only Win 8 on ARM devices that won't support alternative browsers - which Microsoft have said all along will not contain a desktop.

I suppose they could start selling an ARM version Firefox or Chrome app for Metro through Microsoft's App Store. If MS refuse to do that then I am sure a lawsuit would follow - which might have interesting repercussions for Apple and Safari on iOS.

Who cares anyway - is anyone going to actually buy a Metro tablet? I would guess anyone who wants a tablet has already opted for Apple or Android.

Forcing people to use Internet Explorer on tablets is another good reason to avoid Metro, and the lack of any third party addons kills it in the water. I think it says a lot for IE that in Windows 7 MS ask you constantly to disable addons to make it work faster. MS just can't write browsers!

Maybe MS will start giving them away with cornflakes to make their sales look good.

I suppose they could start selling an ARM version Firefox or Chrome app for Metro through Microsoft's App Store. If MS refuse to do that then I am sure a lawsuit would follow - which might have interesting repercussions for Apple and Safari on iOS.

Well if Microsoft makes Surface tablets in cheap cost, trust me i'll buy them. Right now they are super expensive and are suitable for cafes, artistic studios and for other expensive places. As for firefox taking shot on windows, it is obvious that because they're having trouble keeping market against webkit browsers. They have somehow managed to beat IE but chrome is beyond their playground now.

By the way if they make surface tablet with sync feature for office and games, I don't think Ipad hype will remain much. Game syncing between devices is currently apples court and unless microsoft or other tablet companies bring such a feature, Ipad will be hard to beat.

I think not allowing 3rd party Win32 apps (hence FF and other browsers) on ARM tablets is a very stupid move from Microsoft. If recompiled, native Win32 applications worked on an ARM tablet, that would be a big advantage. Without it, why choose a Win8 ARM tablet over Android or iPad? I see no reason at all.

I think not allowing 3rd party Win32 apps (hence FF and other browsers) on ARM tablets is a very stupid move from Microsoft. If recompiled, native Win32 applications worked on an ARM tablet, that would be a big advantage. Without it, why choose a Win8 ARM tablet over Android or iPad? I see no reason at all.

Win32 apps have never worked on ARM on any of the Microsoft mobile platforms. I'm not sure why this non-issue is such an issue. Mozilla made Firefox home on iOS which definitely required development- if they want a browser on the platform, then port their browser to the platform. It would be different if they said that no 3rd party browsers are allowed, but that's not what this is saying.

Presumably Android is open so you can install what you like. I presume Firefox is annoyed that any install will have to be approved by MS through their app store and I guess getting approval is going to be expensive (if MS's past track record on that sort of thing is anything to go by). Also one of the major strengths of Firefox is extensibility - I presume since MS is not going to allow any extensions in IE then any app in the store is likely to haveto adhere to the same principle.

So how come Firefox works on Android? Aren't all Android devices ARM devices?

I am confuzzled.

It's an OS level issue. Consider that Google made the Android OS on the Linux kernel but for mobile devices (helped by the fact that pure Linux has been used in such applications) and that Windows doesn't fit on mobile devices (the mobile environment has always been on a different kernel) and you start to see the difference. I doubt that Windows could be stripped down enough to make it mobile.

While Microsoft does not ban 3rd party web browsers on ARM devices, those browsers (unlike IE) would have to run in a WinRT sandbox. They'll be like 2nd class citizens compared to IE.

Will it necessarily be a WinRT sandbox, or is this just bad information disseminated without knowledge of what it really means? Microsoft is building WOA (windows on ARM), which will support the same WinRT APIs, in addition to having a commonality with Windows on Intel and AMD. (1) They haven't stated whether you can even build for WOA without using WinRT, but it seems so from that blog post- MS is just minimizing word of it in favor of WinRT, which only makes sense from their perspective as changing platforms is a big deal and they want total buy in (and seem to be muscling people to get it). I don't agree with this approach, but I can understand it from a business perspective.

Yes, Microsoft's position is understandable, but I still do not think it is a smart move from them. At this moment, Win32 is still the biggest competitive advantage Microsoft's Windows has over any other OS. Microsoft is victim of its own success. Yes, Win32 is old, it is sometimes painful to use, but it gets the job done and there are countless developers knowing how to create Win32 applications.

Microsoft feels they are slipping behind, because the API of other OSes look so much more modern. They are desperately trying to create a new platform/API to replace Win32. The .net experiment did not succeed, it is now 10 years since it was introduced and there is still no .net-only OS for .net apps. Almost every larger .net desktop application is PInvoking something and would not work in a Win32-free environment...

And now, Microsoft gives the new API/platform another shot with WinRT. While I applaud them they do not want to force a garbage collector on everyone anymore, and WinRT may be a good API, I do not believe they have a good position and marketing power to push it through this way. Developers would have to learn a new API in order to be able to write applications for ARM Windows 8 tablets. If I want to learn a new API, why not make something for Android instead? The Windows brand is strong, but without Win32 backing it up, it may not be enough.

The .net experiment did not succeed, it is now 10 years since it was introduced and there is still no .net-only OS for .net apps.

This, I don't get. I don't think there is a failed experiment there, nor was there the intent for a .net only OS. They never made that push like they are for WinRT. Not so sure it is just about the API either; it seems more a function of the functionality of the OS, and how they see that to have a successful tablet, they apparently need to go the Apple route. They tried the Linux/Android route several times, and Windows just isn't meant to be a tablet OS. Having never used an Android device, I'm not even sure how they pulled it off as Linux is very much more keyboard oriented than Windows, so hats off to them. But if Microsoft has tried it twice and failed miserably both times, then why would they try the same thing again?

Owning platforms in in Microsoft blood, it is their core business. Microsoft more or less owned the DOS platform and made a successful switch to Win32 in the nineties. When the computing power reached the threshold to make windowing OS possible, Microsoft was there with a decent product.

In 2002, Microsoft introduced .net and decided to push it very hard (I was attending a conference back then and it was obvious). They even used the Visual Studio.net name instead of Visual Studio 7 confusing many developers. It is my understanding that their goal was to make another switch, this time from Win32 to .net and then own the .net environment. But that did not happen, there is no obvious advantage of .net over win32 (and some people, including me, still consider Win32 a better choice due to compatibility).

And now, we are seeing another attempt to introduce a new API and replace Win32 with WinRT. If Android and iOS did not exist, Microsoft would have a good chance of succeeding and establishing WinRT as the next API. But they missed the right time. When the computing power and efficiency allowed feasible tablets, Microsoft was not there with the right product. Someone else was.