Is Open Source an Anathema for .NET?
Along with Mono, Novell sponsors several open source .NET applications based on Mono:
Why am I focusing on .NET open source projects? In short, because open source projects are treated as second-class citizens in the Microsoft ecosystem. Many highly popular open source projects have contributed so much to the .NET community, and they've gotten virtually no support at all from Microsoft in return. I'd like to see that change. In fact, I'll go even further-- I think it must change if Microsoft wants to survive as a vendor of development tools.However, some feel Open Source cannot take hold in the .NET community due to the business model used by Microsoft and similar ISVs. Frans Bouma relates:
Open source doesn't need money to become solid, it needs attention. Just throwing money at open source is what MS is doing for years and it hasn't payed off. The reason for that is that the mentality of the average developer on MS platforms is that you simply pay for controls, libraries and tools and if you work on these products, you get payed.Ted Dennison points out another issue when developing on the .NET platform and working on an Open Source project:
THAT is what is lacking in the MS' ecosystem for open source. You can throw money at it, but that mentality won't change. One of the core reasons it won't change is because MS won't let it be changed: if it does change, their days are numbered.
First off, are all the various .NET's licenses one has to agree to in order to work under the system GPL compatible? Microsoft has been known to craft EULAs with the specific purpose of making them GPL-incompatible. I'm guessing there's some way to do it, as a gcc-based Ada compiler has been ported (http://www.usafa.af.mil/df/dfcs/bios/mcc_html/a_sharp.cfm ). However, a quick search online indicates that the license associated with the Ajax controls, among others, is incompatible. According to http://en.wikipedia.org/wiki/List_of_software_licenses , the Ms-PL, Ms-CL, Ms-LPL, and Ms-LCL are all incompatible. I have to read every EULA very carefully to be sure I'm legal.Phil Haack takes an interesting point of view in relation to using a proprietary stack to build an open source application:
I have the vacation view of Open Source. While I would love to be on vacation all the time, I’m pragmatic and I’ll take as much as I can get. Some vacation is better than no vacation.Regardless of the definition of anathema one adheres to, Greek or Hebrew, if the past year is proof, the philosophies of Open Source are taking hold in the .NET community.
The .NET Queue, on behalf of InfoQ, would like to extend an offer to the .NET Open Source community. Let us know about your major release versions and we'll gladly post a product release announcement along with a review.
What about Nant, NUnit and CC.net?
The people who invested time developing or even learning those tools feel cheated in some ways (because for many people, they will just default to using what comes in VS - just like IE is the dominant browser just because its the default for most PCs sold).
I think its a crying shame (I would love to be proven wrong), but its my take, and the reason why I stopped some time ago looking at .Net at all in my (increasingly rare) spare time.
A few additional thoughts
The timing is not much different with .NET. However, one would hope the powers that be would understand and learn from others lessons, especially when it comes to Open Source.
Re: A few additional thoughts
Re: What is the
InfoQ is broken up into communities or "queues". InfoQ = Information Queue, hence the name.
In this manner you can personalize the site to only see content from the communities or queues you sign up for. The left sidebar contains a box labled "Communities" where you can do this customization.
Re: What is the
Re: What is the
Thanks for the endorsement of the InfoQ editorial style, the more vocal our readership is, the better the editors can make the site.
Re: What about Nant, NUnit and CC.net?