SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Pastimes : Dreamers' hideout -- Ignore unavailable to you. Want to Upgrade?


To: Lahcim Leinad who wrote (1356)1/5/2013 9:54:55 PM
From: Lahcim Leinad  Read Replies (1) | Respond to of 2222
 
Methinks this guy is dreaming:
However, what is clear via Google’s statement is that the company intended to limit access to the product for the Windows Phone platform due strictly to performance reasons. This means that the company, yesterday, did not act in a way that was expressly designed to suppress Windows Phone viability as a platform. - Google says Maps redirect on Windows Phone was a product decision, and will be removed - The Next Web
Cause, as I already quoted in the post to which I am replying:
Breaking down the Google Maps – Windows Phone issue | Tom Verhoeff
So what does this mean?Google’s own statement suggests that not supporting WebKit is the problem here, however the experiments mentioned show that there doesn’t appear to be any real problems. Combine this fact with some other recent development like Google removing ActiveSync support for Gmail users and Google still blocking a fully featured YouTube app for Windows Phone. It just shows that Google is just mocking Windows Phone and its users, something TheNextWeb also realized. It’s just another chapter in the ecosystem war.