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 Google.com 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."
Thread beginning with comment 547569
To view parent comment, click here.
To read all comments associated with this story, please click here.
Vanders
Member since:
2005-07-06

The basic maps functionality works without Silverlight, but the "Streetview" equivalent does not:

https://region-b.geo-1.objects.hpcloudsvc.com:443/v1/81913991838883/...

(Chrome 23.0 on Linux)

Reply Parent Score: 2

Nelson Member since:
2005-11-29

No. When Microsoft does it is bad, and when Google does it is bad.

Silverlight had its time, but its obvious the web as a whole has moved on. Microsoft is behind the times if they haven't fully moved to HTML5 yet.

Anyway, that's the critical difference, while some people here can't seem to criticize Google without trying to deflect the blame to Microsoft, others have the ability to criticize both.

Its amazing the amount of people that have suddenly decided interoperability doesn't matter because the company that gets burned the most is Microsoft.

Reply Parent Score: 2

Vanders Member since:
2005-07-06

The problem you have here is that HTML5 isn't a standard, and that Google are using the extensions (-webkit) correctly. Microsoft have no such excuse.

I've not seen such double standards applied since WebM versus H.264.

Reply Parent Score: 3