That is the outright blocking part. The “making it difficult” side of the coin is on the Metro UI within Windows RT. Here Mozilla and Google are developing Metro versions of their Firefox and Chrome browsers, but they will not be given full access to the Windows 32 API (all Microsoft products including Internet Explorer 10 have access to Windows 32 API).
“If we built Firefox for Windows ARM Metro, we would not have access to those powerful Win32 APIs and so we would be at an extreme disadvantage when compared to IE 10 for Metro. We could build a beautiful Firefox that looked really nice on Metro, but Firefox would be so crippled in terms of power and speed that it’s probably not worth it to even bother. No sane user would want to surf today’s web and use today’s modern websites with that kind of crippled browser.”
I understand more now where Mozilla is coming from. They’re worried that Windows RT might actually, you know, succeed. As of now it’s a crapshoot: Windows RT tablets may totally tank when they are scheduled to come out this fall. There is, after all, this thing called the iPad tablet that consumers seem to enjoy using.
If Windows RT devices are greeted with crickets and tumbleweeds, then the point is moot. It won’t matter that Chrome and Firefox can’t run effectively on tablets that nobody cares about. But Mozilla obviously can’t assume that Windows RT will be a lemon. They have to prepare for it to be a smash success.
As Supersite for Windows Paul Thurrot put it in a recent post: “If Windows RT takes off and is truly successful, it becomes Windows. That is, it does what NT did decades ago, existing for a time side by side with what used to be Windows and then eventually supplanting the old Windows.”
If Windows RT does become Windows – and it could – and Microsoft is handicapping competitive browsers, we’ll be partying like it’s 1999. And at this party, Mozilla and Google should cry if they want to.