Having followed a fair number of MS bloggers/podcasts currently in and around their web tools (ASP.NET, MVC, etc) teams... I honestly believe they understand the value of open source.
Visual Studio and their MVC framework continue to impress me (I mostly work in Ruby today, but have to maintain some .NET stuff) and MS takes inspiration from successful open-source tools and frameworks where needed. Many of their recent advancements over the last 3-4 years have clearly been the work of engineers who enjoy and value the best of the open source world.
I'm not trying to tell you that Microsoft is suddenly our warm, fuzzy friend. As even Scott Hanselman would gladly admit, they're ultimately trying to sell you software licenses or Azure services.
But it seems to me that they're using open source the right way in order to achieve that goal, as opposed to the bad old "embrace and extend / embrace and extinguish" days at Microsoft.
Whether or not Microsoft has earned another shot with us or not is definitely up for debate, and with all the cool shit happening in the open source world it's probably even a moot point to an extent.
But they're definitely doing more than cargo-culting in Redmond these days.
I think one would be exceedingly foolish not to exercise the very greatest of caution. This is Microsoft we're talking about - they have a track record of profound fuckery.
But I do indeed think this is better than not having happened.
I wouldn't place bets on any strategy that relied on Microsoft not closing the doors again at some point in the future, on future versions of their development stack.
Like you said, though, this is better than not having happened.
I don't see why they would. This has been an obvious move for a long time, keeping it closed never really made any sense to me. They gained nothing from .Net being closed except hate and utter avoidance from people like me (vocal early adopters.)
MS doesn't really make money off C# or .Net directly, they make money off the windows licenses you need to run the resulting code.
Open C#/.Net = stronger, longer lasting community / free improvements = more users = more licenses.
It also has other side effects like fostering [more] open source frameworks/plugins for their platform, which again, strengthens their position.
Microsoft also today announced that Visual Studio 2013 has sold over 3.7 million copies since its release less than five months ago. That makes it the fastest-selling release of Visual Studio to date.
Based on those numbers and the fact that Visual Studio prices range from about $1,000.00 for VS Professional up to $13,000.00 for VS Ultimate, I'd say they make quite a bit of money of C#, .Net (and of course C++ as well).
At $100.00 a pop those sales numbers would still indicate VS generated sales revenue of $370.00 million.
My guess is the actual revenue figures are probably in the $1B to $2B (B = billion) range, which isn't too bad for a product that I'm sure Microsoft doesn't consider one of their big money makers and a product line that I'm sure they also subsidise with income from sales of their other products.
I too suspect Microsoft looks at VS as an essential, break even product, but with sales numbers like that I can't believe they aren't also making a nice little profit from VS.
Those sales also include MSDN You can buy VS 2013 right now, without MSDN for around $400.00. Still pricey IMHO. But no where near the 1k price-point you referenced.
Curious, what was so bad about 2012? I could barely even tell the difference when upgrading to 2013, aside from the addition of the nifty Peek Definition feature.
I wouldn't call 2012 terrible, but 2013 seemed a marked improvement to me. Little features and enhancements were sprinkled all over the place. Better Blend functionality is one enhancement I've noticed.
VS has been around a lot longer than C# and although anecdotal I would hazard a guess to say the majority of those sales were at massive discount to schools and universities not to mention there is no way they would get 13k a pop in other countries.
Like I said they dont make money off the language or the framework directly it being open source will certainly not hinder or hurt their vs sales. It will most likely increase them.
Releasing .NET sources could help Mono development and ultimately lead to .NET world not being locked to Windows (at least on servers, you'd still want Windows for Visual Studio when doing development)
Unlike GPL2, the Apache license has an explicit patent grant. When I first saw this announcement, I didn't realize what effect it will have on the patents used to bring up any chance they got: they join the patents already available under various approaches (due to C# standardization or the Communit Promise). And I believe you can now avoid the goofiness of all end users explicitly needing to accept the Community Promise.
I know a lot of people who went to work for MS after the .com crash in the 2000's. All of them went in with the attitude that MS needed to get religion on standards and open source. Seems to me that some of this is paying dividends now.
> This is Microsoft we're talking about - they have a track record of profound fuckery.
They have a bad track-record, but not in terms of "this team" (known as Devdiv). They might have gotten all uppity about IE, Windows or what-have-you - but the .Net team had a relatively quick epiphany about open source. Look at Mono.
Java is always touted as a "more open" platform, Microsoft-haters have no issue spewing falsity that the Microsoft encumbrance is a big risk - however, so far as the framework track-record goes, Microsoft has a "community promise", an ECMA spec and has given Mono unit tests for Moonlight; Sun/Oracle has a track record of aggressively pursuing copyright (the recent spat with Google/AOSP).
I'm not saying that Java sucks, or that people shouldn't use it. I'm just saying that a lot of people need to have a hard look at how much time they spend trying to mud the name of a company trying to make a turn. These opinions are antique.
It may change in the future given new governance in those corporates (just as the e.g. Java, NodeJS situation may change), but as of now and as far as .Net FX goes: Microsoft is likely one of the best living examples of how things should be done.
1. Internet Explorer standard compliance : Internet Explorer has introduced an array of proprietary extensions to many of the standards, including HTML, CSS, and the DOM. This has resulted in a number of web pages that appear broken in standards-compliant web browsers and has introduced the need for a "quirks mode" to allow for rendering improper elements meant for Internet Explorer in these other browsers. [http://en.wikipedia.org/wiki/Internet_Explorer]
2. SCO versus Novell : On March 4, 2004, a leaked SCO internal e-mail detailed how Microsoft had raised up to $106 million via the BayStar referral and other means.[60] Blake Stowell of SCO confirmed the memo was real.[61] BayStar claimed the deal was suggested by Microsoft, but that no money for it came directly from them.[62] In addition to the Baystar involvement, Microsoft paid SCO $6M (USD) in May 2003 for a license to "Unix and Unix-related patents", despite the lack of Unix-related patents owned by SCO.[63] This deal was widely seen in the press as a boost to SCO's finances which would help SCO with its lawsuit against IBM.[64][65] [http://en.wikipedia.org/wiki/SCO%E2%80%93Linux_controversies]
>* Internet Explorer standard compliance : Internet Explorer has introduced an array of proprietary extensions to many of the standards, including HTML, CSS, and the DOM. This has resulted in a number of web pages that appear broken in standards-compliant web browsers and has introduced the need for a "quirks mode" to allow for rendering improper elements meant for Internet Explorer in these other browsers.*
For one, this wikipedia page is incorrect (shocker, I know). The "quirks" mode has little to do with "proprietary extensions" in IE, and more with stuff like incompatibilities due to MSs early adoption of standard syntax that later changed.
Second, all browser vendors have introduced "proprietary extensions". Heck, Javascript itself was a proprietary Netscape extensions, as were tons of other stuff we take for granted now. Oh, and this AJAX thing? It started as a proprietary IE extension. Not to mention the Canvas and CSS animations (which started as proprietary Safari extensions).
2. Seems legit (if another example of "ancient history", that didn't even matter in the end).
3. The consortium that had those patents seems to include all major players (even Apple, Blackberry, Sony et co). So not really singling out MS in this.
I would also add that Google, Apple, Facebook and others are hardly without their track records of "profound fuckery"... and yet it's only Microsoft for which the knee-jerk reaction to any bit of news seems to be "it sucks."
Oh come on, did you miss the huge backlash when fb took over occulus rift? And Google get a lot of shit for closing much used and loved services.
But Microsoft wanted to remove the open web, in favour of all their proprietary services, such as Active-X. Places like South Korea foolishly followed the MS paradigm, and they are suffering for it now. Microsoft wanted to control everything, and kill Linux and over open source projects by spreading FUD.
Damn, give it a break those Halloween Documents were over 10 years ago. The pricing thing is one bit, Microsoft hasn't really been too shy about that, but neither has Intel. The whole bundling of IE - how else did you expect someone to browse the web? I don't get it. People don't want IE in Windows yet can never give an answer of how people will get anything else. Then Microsoft has to give people choice. Such a vocal minority.
10 years ago Microsoft was unlike any other big company because of their stronghold on personal computing - being able to use their monopoly on one market to crush their competition in other markets and they did so repeatedly. Startup founders for example always had to take into account the "Microsoft problem".
I don't blame them for bundling IE in Windows, not bundling a browser would be foolish and you can say that Microsoft bundling IExplorer in Windows is what made the web so ubiquitous - I blame them for (1) not making IE cross-platform, which meant that alternatives like, Mac OS, Linux, OS/2 suffered for years because the web was optimized for IE - actually IExplorer was released for Mac OS but it wasn't the same, which made the problem worse as it stopped alternatives for awhile, (2) promoting Windows-only technologies like ActiveX, still in use by many online government services in many countries and (3) after they crushed Netscape with IExplorer 5, which was really good technically speaking, they completely halted the development of IExplorer and of the web in general. IExplorer 6 was a cosmetic release, after which the team was dissolved, many of the members ending up working on Silverlight and other such bullshit. Not mentioning web standards here because the web standards were whatever IExplorer was doing, 10 years ago.
In so far as forgiveness for mistakes that happened 10 years ago - dude, many of us don't have a short memory and many of us don't forgive so easily, not when we aren't seeing signs that a company changed. I'm happy for these recent announcements - it seems that there is interest amongst the upper management to change things, now that Ballmer is gone. And Roslyn (with F# before it) - are the first projects of any significance that they are open-sourcing and F# is finally accepting contributions from third-parties.
But lo and behold - Microsoft is choking Android with patents infringement threats, because obviously, when you can't innovate, you can always litigate, especially when you have a war chest that was built starting in the early eighties. I don't hate patent trolls as much as I hate big companies that are becoming obsolete and with stuffed legal departments that sit on their asses all day thinking of how to "monetize" their bullshit IP, that was built on top of prior art in a time when software patents weren't the norm mind you.
So I'll forgive Microsoft the day they stop threatening and litigating and strong-arm their way into new markets. And don't think that I'm not seeing what Google and Apple are doing. Neither of them resemble the companies I fell in love with years ago. And they should pay attention to Microsoft, as public trust once lost is very hard to regain.
It may have been, but it was dropped on the floor, which happened after Mac OS was using it as the default browser as part of their 1997 deal with Microsoft, to be replaced with Safari in 2003 - pretty late IMHO.
This year's technical excellence can be next year's pain in the ass, as seen with IExplorer. And I don't understand why they haven't open-sourced IExplorer yet.
Shame it was dropped. I am not sure many people would use it now on Mac, given its less than stellar reputation on Windows (although possibly this reputation only exists in nerdy circles and not with the average "normal" computer user).
Safari has always been mostly OK on the Mac (although I tend to use Chromium instead) but on the iPad it crashes a lot for me.
It always makes me laugh the shouts of "NOO!!!" and general disbelief at the Mac conference when IE was announced. The sky was falling. It fell and became glossy and shiny and Apple lives.
Yeah. I get so mad when the default Ubuntu install gives me Firefox. Sure I can always just immediately use FF to download another browser, but it is so anti-competitive! Such monopoly!
Seriously though, you have to have an initial browser to be able to get the browser you want. Of course a company will make that initial browser the one they make themselves. I've never understood the outrage over this.
I had no idea that Ubuntu made firefox an integral part of Ubuntu and that you couldn't remove it. Or other browsers wouldn't run as well as firefox on ubuntu. Geez, maybe Ubuntu really is like Microsoft! Huh, thanks for that.
I don't remember other browsers running less well than IE just because it was built into the OS. If anything, I've always remembered 3rd party browsers running quite a bit better.
Not certain if Ubuntu has a browser built in, but I would say that in this day and age, if GTK+ doesn't have any native components for rendering HTML then that would really stand out. It's considered an essential feature on every other platform's GUI toolkit. Just try removing WebKit from Android or an Apple OS, or pulling Gecko out of a Firefox phone.
The last exhibit would be Microsoft scrapping their plans to ship a version of Windows 7 that didn't include IE. (Though I imagine the rendering engine would still be needed - gotta display help files somehow, after all.) Turns out manufacturers didn't want to carry it, because nobody wants a computer that ships without a web browser anyway.
>> The whole bundling of IE - how else did you expect someone to browse the web?
Requiring IE to download Windows Update is never acceptable. Everybody likes to hate Windows Vista but here is one thing Microsoft got right in Vista (and beyond).
"Microsoft had previously been in discussions with Stac to license its compression technology, and had discussions with Stac engineers and examined Stac's code as part of the due diligence process. Stac, in an effort led by attorney Morgan Chu, sued [1] Microsoft for infringement of two of its data compression patents, and won; in 1994, a California jury ruled the infringement by Microsoft was not willful, but awarded Stac $120 million in compensatory damages" [https://en.wikipedia.org/wiki/Stac_Electronics]
"Judge Thomas Penfield Jackson issued his findings of fact on November 5, 1999, which stated that Microsoft's dominance of the x86-based personal computer operating systems market constituted a monopoly, and that Microsoft had taken actions to crush threats to that monopoly, including Apple, Java, Netscape, Lotus Notes, RealNetworks, Linux, and others." [https://en.wikipedia.org/wiki/United_States_v._Microsoft]
There've been plenty of others since, most notably related to being pro-software-patents and using them to shake down Android OEMs, making threats and creating FUD about Linux, and using exclusive contracts and their leverage on OEMs to ensure that Linux on Netbooks failed (and were hobbled with artificial specification limits, etc.) and that ARM-based notebooks (running Linux) were dropped by vendors like Pegatron and Qualcom despite being highly popular when debuted at Computex... http://www.trustedreviews.com/news/ARM-Powered-Pegatron-Netb... or http://liliputing.com/2009/06/pegatrons-arm-based-netbook-at...
Personally, I've despised Microsoft since I lived in Seattle (doing research in the building next to the Mary Gates wing of the UW Hospital) prior to moving to New Zealand.
I think you have to define "they" here when you say "they understand the value of open source."
There are a lot of people at Microsoft who really do understand the value of open source. When I worked there ten years ago, there were plenty who did. When I wrote interop papers as an outside consultant in 2007, I worked with a unit that did.
But Microsoft also has a bunch of real problems that make it hard for them to realize this value, and so their options in going into it are somewhat limited. They can't pivot and become a services company because their whole Microsoft Partner network would be turned upside down. So they enter services in some key areas where their partners can't. It's a very delicate process, and it means for many on the administration side, the value of open source software for Microsoft is not as high as it would be for some other firms.
Nonetheless this is huge. Open sourcing the VB.net/C# compiler effectively means the possibility of an Linux port, which means that .net has the possibility to become write once, run anywhere even if the whole class libraries are not open sourced yet. This is a gamble for Microsoft because it reduces the barriers to moving from Windows to other platforms (Linux, OSX, BSD, etc).
Outside of my 9-5 work, I've probably deployed nearly as much C# code (via Mono) under Linux as I have under Windows. In a few ways it's been very nice, in others a bit frustrating. I think that if MS Dev-Div buys out Xamarin, we'll see where things are really headed here. It will either be a new era of OSS tools from MS, or back to the old "kill it for cross platform in v.Next" ...
I'm hoping that the tooling and integration gets a lot better in *nix, but nod sure how the Mono license (MIT iirc) and this new C# license (Apache) will jive together.
Personally, most of my new dev for the past couple years has been in node.js (which has its' own niceties and quirks).
> I'm hoping that the tooling and integration gets a lot better in *nix, but nod sure how the Mono license (MIT iirc) and this new C# license (Apache) will jive together.
The MIT license is a lot more permissive than the Apache license. However I see no reason that you can't have different components under each license which work together harmoniously. If nothing else, the MIT license can be easily changed without consulting other contributors because of the sublicensing grant.
It's obvious to me that they see their future as providing an integrated toolset between development and the cloud. They want to build tools that let you push code direct to Azure, and they're becoming more agnostic about whether or not that is a microsoft stack code or other code.
They renamed it from Windows Azure to Microsoft Azure to remove the windows connotaiton - specifically mentioning that 15% of all Azure deployments are Linux OS. So I would say that this is where they see the future, although there are still some very byzantine sales processes to go through to buy enterprise azure, because of the existence of the partner network. In that sense, they're almost like the car manufacturers forcing you to buy through a dealer for their direct-to-consumer products.
Well, I'd like to see Visual Studio for Linux with support for Java, Scala, Clojure, Haskell and other non-Microsoft technologies. That's my wishlist in this bright new era of Microsoft openness.
I don't like Microsoft but Visual Studio is the only IDE I've ever tried that is substantially better than gedit/jedit. The auto-completion (intellisense) is just delightful to use.
Is Visual Studio auto-complete significantly different from IntelliJ or Eclipse? There are many great editors an the continium between gedit and Visual Studio, such as Sublime, hell even vim and emacs have autocomplete plugins.
Microsoft does great work in researching static code analysis, I only remember their auto-complete ten years ago for C++ code and it was miles ahead of anything else. It pops up in just the right moment and it just feels like a genuine "code assistant" instead of just an auto-complete. Unfortunately I don't really trust MS with developing great OSX software (see MS Office for Mac) so I'm not sure I'd want Visual Studio. But if they could pull of a proper port, it would be awesome.
Excel for Mac doesn't have the "Evaluate Formula" function and the Name Manager is crippled... (to name a few issues) Makes it really hard to do complex and robust development.
The auto-complete is truly wonderful. XCode's isn't too bad (but does anyone know how to get it to pop up the parameters in a function, same as VS Ctrl-Shift-Space????) but the real stinker I had to use was Borlands Codegear 2007. That whole think was rubbish and engaged in colossal disk-churning for auto-complete. The linker crashed and the IDE was buggy as anything. A shame.
But VS auto-complete was a breath of fresh air afterwards.
While I really like using MS Office 2013, I just can't use MS Office for Mac. It doesn't seem to integrate with the OS very well. I hope that the next version is better - hopefully retina screen support
I agree, it's painfully slow for anything but simple tasks. My former company (in)famously does everything in Excel (including Gant and flow charts), and being the only guy with OSX the load times were terrible, the UI sluggish and it crashed often. I was really quite surprised how snappy the UI was when looking at a coworker's windows box.
It's fuzzy and instant. If you type "flow" it will treat it as if you searched for "stream". You don't need to know what things are named. You just search for what you think it may be and 9 times out of 10 intellisense will find what you're looking for. It's like having Google doing autocomplete for you.
I can't speak for IntelliJ (can never get the damn thing configured correctly), but Eclipse's autocomplete leaves a lot to be desired. This may be configurable, but my experience has been that it's finicky about when it will trigger.
I appreciate Eclipse's openness (and I tend to work with open source languages), but I must admit that purely examining the quality of the tool, Visual Studio is leagues ahead.
I use both on a daily basis, and VS + Resharper beats the crap out of IntelliJ, IMO. My opinion might be different if I had to pay for my licenses, but independent of cost, VS wins.
> Well, I'd like to see Visual Studio for Linux with support for Java, Scala, Clojure, Haskell and other non-Microsoft technologies.
Which is exactly what you can now create using the Roslyn technology that is now open sourced. Add these languages and they will get all the fancy support that Visual Studio provides, like (remote) debugging and code completion.
Perhaps the lieutenants and the rank and file are less afraid of having a chair thrown at them nowadays followed by a firing. And given that the new CEO is from the Azure team it seems like he should know the value of this kind of step.
I mostly feel sympathetic to the engineers working there. It's no fun living under an embarassing dictator.
There's a reason why Visual Studio continues to impress you.
I once saw a presentation of the Visual Studio lead in Belgium, where he claimed that there were over 1200 people involved in the Visual Studio project.
If that's true, i don't think there is any IDE that can top that number and it explains why Visual Studio is the best tool for (almost any) job.
People should realize that Visual Studio is not solely C#, it's NodeJS, PHP, Mono, Python and so much more in one environment.
I don't know, I see this as a good sign but for me it's still "too little too late". At least release it under a copyleft license, make it usable with previous versions of Visual Studio (it only works with 2013) and I'll feel more confident that you aren't setting a trap.
Non-copyleft licenses can easily align with the "embrace, extend, extinguish" strategy. The value of .NET for most developers is closely associated with Visual Studio. They can make the next version closed source and have Visual Studio only accept that one and we are back to the same old Microsoft. Sure, you'd still have the previous open source version, but who cares when most people will probably just move on to the next.
> Non-copyleft licenses can easily align with the "embrace, extend, extinguish" strategy.
What? I would think if anything giving everyone else a crippled license while retaining copyright etc yourself that would be an even bigger setup for a EEE.
Remember, MS can do w h a t e v e r they want with that code anyway it is not lke they'd be bound by a copyleft on their own code.
(Unless they also started accepting patches without copyright assignment I guess.)
Exactly. There's a reason why more restrictive licenses are more conducive to dual licensing models than less restrictive ones.
A non-copyleft license effectively means that Microsoft, should they try EEE, has to compete not only with free as in beer and free as in freedom, they also have to compete with all the closed source competition they are subsidizing in this effort.
If you believe that more competition is good, the less restrictions on the code from a big vendor, the better.
Copyleft licenses are more conductive to dual licensing because they give you no other choice if you want to sell a closed source premium version. That's the only reason. And for that to work you have to get copyright assignment.
I think your view is pretty naive. They develop the platform and own the IDE that's synonymous with it. They can keep any other compiler off the IDE if they want that, you would be competing with them at their house, which is doomed to fail.
With copyleft without assignment at least any later version would effectively remain free for all, whether Microsoft wants it or not. You don't have to believe and hope, it's just the way it is.
You can think what you will about my opinion but it is based on a decade-long career around both BSD-licensed and GPL-licensed projects.
> Copyleft licenses are more conductive to dual licensing because they give you no other choice if you want to sell a closed source premium version.
And the licensor can always decline to sell the license to a competitor though this might be problematic for a big company. The point is that the GPL gives a company control over proprietary spinoffs, while the BSD license does not.
> They can keep any other compiler off the IDE if they want that, you would be competing with them at their house, which is doomed to fail.
Frankly their choice of licensing makes no difference in what sorts of products they can ship.
> With copyleft without assignment at least any later version would effectively remain free for all, whether Microsoft wants it or not.
But the point is that you end up with less competition under a copyleft license because fewer forms of competition are in line with the license. If your fear is against Microsoft as competitor, giving up more rights is better than giving up fewer.
You say you think my view is naive, so I have to ask: how does one both release code under the Apache2 license, a license which allows anyone to change the license and add restrictions when distributing it provided that the license restrictions in that license are met, and adopt an embrace-extend-extinguish strategy. The first two might work ok because one could sell additional proprietary features just like anyone else, but the final one doesn't work because you are competing against yourself if you do that.
Well, I was surely thinking about the option without copyright assignment. Everybody giving assignment to Microsoft? Yeah, that's a bigger and much more obvious trap.
I don't understand what was so upsetting about my previous comment thatgot so many downvotes. Microsoft has a history of being hostile to FOSS. I will agree that they have changed their attitude when they make a serious effort to assure us that there aren't potential traps in this move. Otherwise I'll say thanks but no thanks.
> I don't understand what was so upsetting about my previous comment thatgot so many downvotes.
Didn't downvote but I think the ones who did did so because they found your comment misleading. I happen to agree with them but chose to explain the reasoning behind it instead of downvoting.
Read einhverfr's comment again, espescially the "the less restrictions on the code f r o m a big vendor, the better.".
See, some of us has had to work within and around various funny and not-so-funny licenses for years. Both commercial but open source as well..
Thank you. I think I understand what you say but I simply disagree. einhverfr worked at Microsoft but it's fallacious to think that his view can't be naive because of that.
For me copyleft without assignment is the safer choice, the others depend on future goodwill or a view of the market self-regulating which I don't see happening with such a big gorilla. After the clarification about assignment, I don't see how it's misleading or wrong in any way. If copyleft licenses can be abused in certain situations it doesn't mean non-copyleft ones can't or are the better option here.
I'm interested but worried about the long term viability of this free compiler. I don't want to depend on Microsoft getting the value of FOSS or not. They can give guarantees today that even if they change their mind tomorrow they can't go back in this decision.
I know copyleft licenses can be a pain and that they have problems on their own. I use GPL and LGPL software daily, so I know it. But those issues are orthogonal to the one I'm talking about here (the guaranteed free access to future versions to the community).
And sorry but unless we are talking about another software giant, there's simply no way Microsoft could feel threatened about a third party version of the compiler which works on their framework which is used by their IDE on their OS. They either don't mind what you are doing, will replicate it easily or if everything else fails will keep you away from their framework or IDE.
But I'll shut up as my opinions are continously downvoted by some who can't be bothered to explain even why. I saw some perfectly reasonable comments by einhverfr downvoted too, so it's not just me. I feel HN is becoming toxic. Thanks anyway for the response.
Visual Studio and their MVC framework continue to impress me (I mostly work in Ruby today, but have to maintain some .NET stuff) and MS takes inspiration from successful open-source tools and frameworks where needed. Many of their recent advancements over the last 3-4 years have clearly been the work of engineers who enjoy and value the best of the open source world.
I'm not trying to tell you that Microsoft is suddenly our warm, fuzzy friend. As even Scott Hanselman would gladly admit, they're ultimately trying to sell you software licenses or Azure services.
But it seems to me that they're using open source the right way in order to achieve that goal, as opposed to the bad old "embrace and extend / embrace and extinguish" days at Microsoft.
Whether or not Microsoft has earned another shot with us or not is definitely up for debate, and with all the cool shit happening in the open source world it's probably even a moot point to an extent.
But they're definitely doing more than cargo-culting in Redmond these days.