>> Please read and inform yourself - your ignorance is painful to endure.
You’re a snotty little puke, aren’t you?
>> This doesn’t just affect people writing Browsers, it can and will affect many 3rd party developers.
Well, actually no, it really *won’t* affect non-browser developers much at all. Maybe you could cure *your* overbearing ignorance by delving into some articles with more technical meat in them. Here’s one that treats the issue more fairly, although it’s significantly more technical than that Fox News (snort!) crapola you peddled, and so may be beyond your rather limited technical grasp.
Now go back to Occupying Seattle or whatever trivial pursuit whiles away your day.
And if you would read the source you gave, you would see
Todays web browsers need deep, deep access to operating systems and hardware. On Windows RT, it appears right now as though only Internet Explorer will be given that kind of access. Back in February, Steven Sinofsky posted that apps for Windows RT (Windows on ARM at that point) had to adhere to a different set of rules. Code that uses only system or OS services from WinRT can be used within an app and distributed through the Windows Store for both WOA and x86/64.
You just confirmed what I've been saying for quite a while. MSFT is withholding and locking developers out of RT, this is what was challenged in United States v. Microsoft - as I've repeatedly mentioned (and you've repeatedly failed to comprehend).
Do try to learn, put on the Big Boy pants and think before you post. I don't know what you are talking about - you keep making MY point, then attacking and sounding more and more ignorant with every attempt.