Linked by Thom Holwerda on Sat 5th Jan 2013 14:53 UTC
Talk, Rumors, X Versus Y And so this situation is starting to get ridiculous - and consumers are, as usual, caught in the middle of it all. Google has just blocked Windows Phone devices from accessing Google Maps on their phones. In addition, it also seems Windows Phone users are now restricted to the basic HTML version of the mobile GMail website. While understandable from a defensive perspective - Microsoft's extortion scheme targeting Android device makers and all that - it's still a massive dick move that only hurts consumers. Update: the media attention has worked - Google is backpedalling, and will remove the redirect. "We periodically test Google Maps compatibility with mobile browsers to make sure we deliver the best experience for those users. In our last test, IE mobile still did not offer a good maps experience with no ability to pan or zoom and perform basic map functionality. As a result, we chose to continue to redirect IE mobile users to where they could at least make local searches. The Firefox mobile browser did offer a somewhat better user experience and that’s why there is no redirect for those users. Recent improvements to IE mobile and Google Maps now deliver a better experience and we are currently working to remove the redirect. We will continue to test Google Maps compatibility with other mobile browsers to ensure the best possible experience for users."
Permalink for comment 547691
To read all comments associated with this story, please click here.
RE[7]: Why does HTML5 exist?
by lucas_maximus on Mon 7th Jan 2013 19:25 UTC in reply to "RE[6]: Why does HTML5 exist?"
Member since:

The thing is that we will have have every popular browser code base funded primarily by two large corporations (Google and Apple), and Webkit will become the defacto standard instead of IE.

This will actually split web-standards yet again into two browser groups and we will have the browser wars all over again.

Microsoft supply IE because their corporate clients demand it (usually for Group Policy and the slower release cycle which let said clients develop intranet applications against a set of features that won't change while the browser and OS are still supported).

So you will have Webkit based browsers, IE and then you will have 3rd and 4th place to Opera and Firefox. Microsoft will still hold on to their corporate clients and like before there will be two different browser code bases being utterly incompatible when it comes to client side abilities.

What will happen is the opposite of what you want.

Reply Parent Score: 2