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 547615
To read all comments associated with this story, please click here.
RE[7]: Stupid Google
by Nelson on Mon 7th Jan 2013 00:21 UTC in reply to "RE[6]: Stupid Google"
Member since:

You can't. Mono/Moonlight is supposed to be the "universal" .NET/Silverlight for UNIX and UNIX-like operating systems, but its very existence is more of a joke than anything.

In fact, it appears that Microsoft themselves used their typical EEE "extend" tactics to extinguish it. Big shock!

Moonlight ran most that I threw at it back in the day, but obviously its stagnated in the past few years. Then again, so has Silverlight. Times change, the web Changes, and Silverlight changed mid-way through its life time.

The issue with Moonlight was the stigma associated with Mono hurt them when it came to finding people interested enough to maintain it. It wasn't that of a lack of interoperability (Microsoft made available to test test suites and notified them in advance of pending changes to Silverlight), but one of a lack of manpower.

Silverlight started out as a RIA plugin (back when those were popular) because TBH every other alternative (Flash, JavaFx, HTML5, Air) sucked balls at doing it in a RAD fashion.

However this fad slowly faded, then it kinda settled in to be a Flash competitor, and had some limited success as a proprietary streaming solution way during the HTML5 video rise.

Then after that, it settled into a kinda niche where people can write pretty full featured Line of Business apps with it, and many people still do.

It also still powers Windows Phone 7, and it's a hybrid platform in Windows Phone 8. Windows 8's WinRT is based off of Silverlight's DNA. It's been evolved into a general purpose framework for Windows.

Basically this was a long, drawn out journey for Microsoft to build itself a platform that would form the foundation for its OS moving forward. The way it got there was pretty fucked up and crazy, but its there.

Reply Parent Score: 2