Linked by Thom Holwerda on Sat 25th May 2013 00:45 UTC
Google "So in summary... Google has pulled the plug on support on a protocol they've helped popularize, after years of promising interoperability, for reasons that are dubious at best, and in a way that leaves people who don't jump to the new Hangouts app unable to talk to their contacts without any feedback that their IMs aren't getting through... And they've done that with no warning to anyone. I imagine there's a bunch of people out there wondering where some of their buddies have gone, or why their messages aren't getting responses, because this isn't documented anywhere." Google really messed this up. Such a dick move.
Permalink for comment 562854
To read all comments associated with this story, please click here.
RE[5]: Comment by marcp
by Nelson on Sun 26th May 2013 15:05 UTC in reply to "RE[4]: Comment by marcp"
Member since:

That support is a result of Linux already having a huge presence in typical VM workloads, as such not supporting Linux on Azure would be commercial suicide.

Are you seriously trying to pass that off as evidence of Microsoft not being about vendor lock-in?

Yes, because it is exactly the opposite of what you claim. You have a high degree of choice on Microsoft's cloud offering.

I'm sure, just as they were incredibly active when they bribed their way in getting OOXML accepted as an ISO standard.

Do you have any evidence that they're doing anything shady on the W3C? Their performance monitoring stuff just reached candidate recommendation. They're also responsible for some Touch Events stuff going into WebKit and Blink, and pushing it forward at the W3C level.

Do you forget about their work on WebRTC? The work they've done on HTTP2.0 including SPDY support in IE11?

Hell, they brought Node to Windows.
How is any of this lock in? You don't get to say "Well its popular anyway so they had to" because that isn't true at all. Microsoft has consciously plotted this course for themselves, and contribute to open source software quite frequently.

Whatever the '.NET scene' is 'pivoting' to is not due to Microsoft, how about they open source .NET and allow it to be ported to any platform? Now that could indeed be construed as them 'pivoting' towards open source.

Microsoft open sourced ASP.NET MVC which is the largest single component of .NET next to WPF. I wouldn't expect you to know that, given your aversion to anything Microsoft.

Also .NET is a ECMA standard with the internals of the C# language, the XAML vocabulary, and CLR/CIL stuff being fully documented and regularly updated.

People like you conveniently forget that Mono exists and is supported by Microsoft. Hearing people like you talk, and then attending a Mono event sponsored by Microsoft last year shows something starkly different to your invented reality.

.NET actually represents Microsoft's open source initiative rather well.

Microsoft has OSI approved licenses for their free and open source software, and promotes .NET projects as OSS on their CodePlex website. Which has Git integration.

TypeScript is open source. Roslyn (their next generation C# compiler as a service and syntax transformer) will be open source.

They've teamed up with HortonWorks to make a Hadoop distribution for Windows Azure.

All of their Azure SDKs are open source. That's Java, Node, .NET, PHP, etc.

A lot of their Windows 8, WPF, and Silverlight patterns&practices (Prism, Kona, CAB) are all open source software and have been since like 2006.

The Dynamic Language Runtime, a major part of .NET which enables IronPython, IronRuby, and IronPHP among others is completely open source software. IronRuby itself is open source.

Large swaths of .NET such as the Rx Framework and MEF for composition are open source.

So thats' what I mean about pivoting to open source in .NET, again, something you'd understand if you did this for a living. Which you don't, so your interpretations of the facts is at best unwillfully ignorant.

NuGet, their package management system for Visual Studio is open source. CoApp is a way to author and publish open source components is open source.

I'm having a hard time understanding how you could possibly objectively arrive at the conclusions your'e arriving at.

How is Google 'abusing' open source? As for using open source for their own agenda, certainly, just as every other company out there which uses open source.

This is exactly the point. Google is no different from Microsoft in this regard in that they use open source when it lines up with their business model. I have no illusions about why Microsoft chooses to make something open source.

Google however also gives a lot back to open source, which is something that can't be said for many companies.

This screams of a rationalization for why your beloved company has started acting out in the open. This is exactly the thing that I said would be happening in short order from Google. To take the gloves off with Microsoft as they seem intent on doing, you need to play dirtier. Microsoft also has ways to make your air your laundry in public (as they did when they baited Google into sending a C&D over the YouTube app which showed how petty Google was).

They simply can't expect to play hardball and keep up that silly little saint routine that people like you keep falling for.

Certainly not Microsoft whose 'open source initiatives' as you described them are extremely weak at best, but furthermore has a long history of actively trying to harm open source and open source projects.

Extremely weak because you choose to understate their significance on an online discussion, not weak because they're actually weak.

Coming from a Microsoft fanboy it makes you sound like you suffer from Stockholm syndrome.

Uhuh. I really don't envy your position, having to eat crow and all, but this has little to do with me.

You were the one who was so incensed that Google could possibly be acting like a normal company that you tried to drag Microsoft into this.

Reply Parent Score: 4