4 ms·

I'm pretty shocked that Microsoft hasn't been better at maintaining appearances for the EU. If I was on that team (easy to say, I know), I'd make darn sure that

I'm pretty shocked that Microsoft hasn't been better at maintaining appearances for the EU. If I was on that team (easy to say, I know), I'd make darn sure that third party browser developers were kept in the loop. Publish the info on MSDN. Shower them with emails asking them if they need help. It's good for the OS, the public, and it would be a good proactive measure toward maintaining regulatory compliance.

cooldeal 15y ago
The OS isn't even ready yet and they're probably tweaking the brand new full fledged API that's probably full of bugs and issues and has to run on a completely new platform for Windows, ARM and also has to be battery efficient. You're underestimating the amount of work it takes port tens of millions of lines of code into a new platform and then to make sure things work and still have the ability to radically change things to get the last bit of performance out without having to worry about third party developers who have already invested significantly in the beta APIs. Since they have already committed to allowing 3rd party browsers, I guess they will be coming forward with the information when it's ready. Till then the desktop browsers will continue to work for x86 based machines.
- sad_panda 15y ago
  They are at public beta now; fundamental things like API interfaces should have been fully baked months ago.
  - cooldeal 15y ago
    The API for WinRT is fully baked since it's a sandboxed API, but the native code that browsers need is still somewhat in flux I think. Also, that's for x86 only. ARM devices are nowhere as polished. In fact they seem to have specifically made them unavailable and locked them up in glass boxes at BUILD and also didn't allow reporters to play with them at MWC. http://www.engadget.com/2011/09/14/nvidias-kal-el-reference-tablet-running-windows-8-at-build-eyes/ http://www.engadget.com/2011/09/14/nvidias-kal-el-reference-... Maybe they're concentrating on Metro apps first since the browser developers have significant resources to ramp up development unlike the small app developers, I am not sure though.
josephcooney 15y ago
I'm pretty sure the IE and Firefox teams get together regularly. I don't think the same sense of comraderie exists between the IE and chrome teams.
- sad_panda 15y ago
  Not that I know any of the parties, but what makes you think that?
  - btn 15y ago
    Perhaps the (formerly) regular release cakes that they exchanged: http://en.wikipedia.org/wiki/Firefox#Response_from_Microsoft http://en.wikipedia.org/wiki/Firefox#Response_from_Microsoft

cooldeal 15y ago

The OS isn't even ready yet and they're probably tweaking the brand new full fledged API that's probably full of bugs and issues and has to run on a completely new platform for Windows, ARM and also has to be battery efficient. You're underestimating the amount of work it takes port tens of millions of lines of code into a new platform and then to make sure things work and still have the ability to radically change things to get the last bit of performance out without having to worry about third party developers who have already invested significantly in the beta APIs. Since they have already committed to allowing 3rd party browsers, I guess they will be coming forward with the information when it's ready. Till then the desktop browsers will continue to work for x86 based machines.

sad_panda 15y ago
They are at public beta now; fundamental things like API interfaces should have been fully baked months ago.
- cooldeal 15y ago
  The API for WinRT is fully baked since it's a sandboxed API, but the native code that browsers need is still somewhat in flux I think. Also, that's for x86 only. ARM devices are nowhere as polished. In fact they seem to have specifically made them unavailable and locked them up in glass boxes at BUILD and also didn't allow reporters to play with them at MWC. http://www.engadget.com/2011/09/14/nvidias-kal-el-reference-tablet-running-windows-8-at-build-eyes/ http://www.engadget.com/2011/09/14/nvidias-kal-el-reference-... Maybe they're concentrating on Metro apps first since the browser developers have significant resources to ramp up development unlike the small app developers, I am not sure though.

josephcooney 15y ago

I'm pretty sure the IE and Firefox teams get together regularly. I don't think the same sense of comraderie exists between the IE and chrome teams.

sad_panda 15y ago
Not that I know any of the parties, but what makes you think that?
- btn 15y ago
  Perhaps the (formerly) regular release cakes that they exchanged: http://en.wikipedia.org/wiki/Firefox#Response_from_Microsoft http://en.wikipedia.org/wiki/Firefox#Response_from_Microsoft