Microsoft Opens Code Just Slightly More
ctar writes "This story on Bloomberg.com details Microsoft's new program to open the source to parts of Windows in order to compete with Linux, especially in the government sector. Microsoft's spokesman is making these announcements directly: They say governments involved will be invited to Redmond to meet w/ security engineers, and view testing procedures. Countries will also be able to incorporate their own encryption schemes 'based on Microsoft's software'."
Still, if they're going to open up stuff I'd say let me look at IIS, MSMQ, WMI, COM+ and all that other middleware that I tend to hit a lot more... looking at the kernel would be an educational trip - but only that. Not really useful per se.
I think this is a good reason why the term "Open Source" can be extremely misleading. Next thing you know, we will have an "open source" version of windows 2004---however, the license agreement restricts anyone from incorporating their source code into non-microsoft programs, and they will sue anyone who tries to. However, they can go ahead and call their software "open source," because they are making the source code available to the public.
r eedom.html
This is damaging! We must not group together "free software" programs with "open source" ones, for this very reason! The more we call "Linux" Open Source, the more we will be giving Microsoft free advertising for their "open source" programs that will surely be coming out in the future. Please call GPL'd and GPL compatible software "free" or "Libre" in the least, so that we can make clear distinctions between "open source" and the freedom that come's with GPL-like programs. Thank you.
For a more clearly articulated argument see: http://www.gnu.org/philosophy/free-software-for-f
Until it's compiled. Not that I'm saying that Microsoft are a bunch of lying, cheating weasels. I don't have to say that, a couple of courts have done it for me.
Given that, and given the "other arrangement" that the US gubmint has to access the source (note "the" source, not "some" source), I would have no confidence that anything shown to me by Microsoft - in a Microsoft lab, controlled by them, not available for tinkering or compiling - actually represented the source used to build the version of Windows that I was deploying across my home nation of Elbonia.
If you were blocking sigs, you wouldn't have to read this.
http://news.com.com/2100-1001-966219.html?tag=rn
Here is Microsoft's SEC Filing:1 03221002001614/d10q.htm
http://www.sec.gov/Archives/edgar/data/789019/000
Quite easy to find:2 3&mode=nested&tid=109
http://slashdot.org/article.pl?sid=02/11/17/20372
By the way, someone posted about Microsoft opening source code to India.. Slashdot had an earlier story here:5 5&mode=nested&tid=109
http://slashdot.org/article.pl?sid=02/12/12/20462
Another slashdot article on the XBox losing money:3 4&mode=nested&tid=109
http://slashdot.org/article.pl?sid=02/11/15/15192
Amazing what turns up when you do just a little bit of research. ;)
user@host$ diff