Microsoft Planning on Opening Up More Source
mhh5 writes "It's a bit surprising, but it looks like Microsoft is considering making some of its code open source. Obviously, Microsoft's OS or Office are not going to be opened, and it seems like Microsoft is just trying to get more developers, but it's a interesting change of policy."
I can't wait to get my hands on that DOS 3.3 source. I shall build the mightiest DOS EVER!!!!
Any program MS could open the source to other than Office or Windows is almost completely useless. What would be much better is if they opened the file formats. Then maybe we could have proper .doc readers and writers.
MS is not doing this because they believe in helping mankind. This is a way to get ppl hooked on the shared source and more importantly, having an ability to sue said programmer down the road, if they move over to GPL code.
I prefer the "u" in honour as it seems to be missing these days.
...it's just a bunch of "if-else" loops anyway. Millions. Although, they iterated an array once that and used a "for" loop pretty nicely...
While we know Microsoft are not going to open source anything critical, one of the things they do seem to be starting to do is make the development process more transparent to the public.
Many Microsoft developers now discuss projects openly on Blogs and Forums, and some projects (i.e. Internet Explorer) now have community sites where the public can interact directly with the development team.
Personally I like this transparent process, and hope it becomes popular within Microsoft. They have some of the best developers in the world and this sort of restructuring could lead to some excellent software being produced.
That's what it's all about.
Microsoft finally takes a step in the right direction, and you still critisize. Give them them the credit they deserve, it may not be much, but it is better than them raping the world.
Why can I not mod a message to crap?!?
It's a trap!
...ok, dumb jokes aside, this is probably not as good as it sounds. I'd advise the Wine guys to stay as far away from this code as possible!!
Remember, these are the guys who "recommended" Baystar to SCO. They are NOT open source friendly.
SCO caused Linux a lot of problems with their whole "code pollution" bit. I'll betcha they're planting seeds to do the same thing with their own code base later on down the road.
Stay away from this, folks. FAR away.
Weaselmancer
rediculous.
I find it interesting that Windows is so widely deployed, yet so few people are truly "in love" with the operating system. You'll find people willing to die for Mac OSX, for OpenBSD, for BeOS, for Amiga, for Gentoo, or for any number of other systems -- but to date, I've never met a single person that was truly satisfied with Windows, much less happy or fanatical about it.
People use Microsoft for a number of reasons, none of them at all related to customer satisfaction. Corporate desktops are assumed to be running Windows with Office unless stated otherwise. Data centers are assumed to be running some Windows server edition, to let the admins use Group Policy and other platform-dependent tools that almost make managing those desktops bearable. People use Microsoft because of their monopoly, and Microsoft exploits this.
And remember, no one got fired for choosing Microsoft.
Thousands of open source developers around the world would die as their head's exploded.
We used to have a joke at Bell Labs regarding the source code for the 5ESS. If we ever wanted to eliminate any competition, we would send them a copy of the source, and they would go bankrupt trying to figure it out.
"To those who are overly cautious, everything is impossible. "
...Although, the possibilities of porting MS Bob to LINUX are intriguing...
HA! I just wasted some of your bandwidth with a frivolous sig!
They are going to open the source of their network protocols. The first thing they are opening is the TCP/IP protocols. ;-)
PENAROL: Seras eterno como el tiempo y floreceras en cada primavera.
It's pretty obvious, and the Slashdot post mentioned it also -- to get more developers. The Windows operating system is unique, in sense that it is very user-friendly and everyone's software runs on it. The reason why Microsoft does not port software to other operating systems is common sense -- Windows is nothing without the software that it has, but that rule applies to any other operating systems as well. That's why Microsoft gives away development tools, because they want people to develop code under Microsoft's name... and this is no different. When people take Microsoft's opened source code and change it around, they are only helping Microsoft's opened source code and Microsoft themselves. It's not really about Microsoft making more money directly, but they will get more developers once everyone starts seeing their technique of programming and that will get them money in the long run.
Just my two cents, heh.
"Instant gratification takes too long." - Carrie Fisher
Microsoft opened up lots of it's source last year, lest we forget. :)
This is purly a business move aimed at PHB's. IBM has made money telling people that Open Source is good and MS is getting in on the right for free.
It could also be that they are trying to get in on the good side of budding developers. I don't know any other CS majors that use Windows on their main desktop and I know of no CS majors who write their code in Windows. At Georgia Tech everything in class is done in Linux after the first Scheme class. If the future coders don't know Microsoft stuff they won't use it or push it in their jobs.
There is nothing wrong with being gay. It's getting caught where the trouble lies.
Liberals call everyone Nazis yet they are the closest thing to it.
Common Public License, or CPL, from IBM. But is all written in legalese, not sure what will that imply in plain words. At least they are saying that this is an open source license, to make a difference with Shared Source that is definately not.
Well, a bit of Googling turned 'em up: Windows Template Library (WTL) and Windows Installer XML (WiX).
There ain't no rules here; we're trying to accomplish something.
A step in the right direction? This? No, this is not a step in the right direction. This is them releasing a bunch of code under a GPL-incompatible (and certainly BSD-incompatible) license. The code is open, certainly, but not free. Which means that while we can possibly submit patches, etc, to Microsoft, we cannot fork it or even use small pieces of it (even if they were written by someone else in the community) in our own code.
The GP was absolutely right: they just want free development. They hope that we will hack their code, but it's still their code. All of it. You can't reuse it. You can't change it. You can't fork it. It's absolutely useless. Even studying it is dangerous: if you looked at their code and then implemented something free (as in freedom) that did the same thing, they could probably claim that you're violating their IP/copyright because your code isn't "cleanroom".
Open source non-free software is very dangerous for the community, because we cannot use it, or be inspired by it -- and yet it's there, like Pandora's box, waiting to be opened. And since so many people confuse open source with free, it isn't long before some well meaning coder takes a bit of their code, edits it, and submits it somewhere else.
They have just forced us to be even more vigilant. Don't you see that we get nothing at all? No rights? No freedom? But they get everything. Our manpower, our mindshare, everything. For nothing.
This is worse than not good. It's evil. A perverse bending of the free software model.
This is like Sauron giving rings to all the elvish and dwarven kings in order to enslave them.
Yes, I'm a nerd.
Still criticize them? Strange, since I've never posted anything criticizing them before (check my comments if you don't believe), perhaps you meant that the internet community in general still criticizes them? No, that still wouldn't make sense since I only posted my own opinion rather than a blanket statement attempting to speak for everyong. Nope, I'm sorry, but I have to call shennanigans on your post. CI
but it's a interesting change of policy
This change is not from today, the change started with WIX under the CPL.
Anyway, if you make a CPL program better(and if it's not yours) you can't earn money with this, only if it helps you to make other things, but who created the program can earn money with your code.
The want the media atention and to be the good guys with this things. Them whem someone talk about Microsoft be against open source software they will say: "we released XX softwares under open source licenses, how we can be against our softwares?"
I was going to make a crack about how obvious this comment was, but you got me thinking about the success of Micro-Soft's marketing campaigns.
Micro-Soft has managed what seemed to me to be an impossible task; turn the obvious security advantages of Open Source into a debate about who has the better security. There are actually people out there convinced that Windows' security is superior due to the success of their marketing, contrary to all reason and evidence.
Micro-Soft have managed to turn TCO into a debate about which is cheaper, Windows or FLOSS, despite the fact that it is blindingly obvious that the cost of Windows is a gazillionfold.
Perhaps your comment is the first of many, as "Micro-Soft supports Open Source" and "Shared Source and Open Source are the same thing" become the new frontiers in their reductio ad absurdem marketing campaigns that seem so successful with the gullible.
Beep. Wrong.
They have stuff under the CPL, such as WIX.
The SSI is something else, it is aimmed at companys, and includes stuff like WinCE.
Wow, I should not post when knackered.
From the article:
I would argue that the GPL has "clearly delinated ground rules", and I'm not sure what extra value is added by the CPL. The FSF licence list gives some hints that the CPL imposes extra requirements:
Does anybody have any examples of why a corporation would prefer the CPL to the GPL?
How is this a change of policy? Let's look at Microsoft's old methods:
1) Embrace new methodology
2) Extend new methodology in a way that locks users into Microsoft products
Let's look at Microsoft's take on "open source":
1) Embrace OSS' idea of providing developers access to source code.
Would anyone care to guess what step #2 will be?
Somebody get that guy an ambulance!
WIX & That Other Microsoft One are released under the CPL.
Wow, I should not post when knackered.
void main() {
//
//**Secret Proprietary Microsoft Code Removed**
//
while (true) {
if (rand() % 2)
doCrash();
}
}
Thus far MS has used the CPL for its OSS projects.
Which (take a look at the URL) is OpenSource.
The SSI is a different beast.
Wow, I should not post when knackered.
This led to the question of what is the CPL and how does this differ from other licenses. A little Googling on my part turned up this site that compares the open source licenses.
The most significant difference between the CPL and the GPL involves the license of derivative works.
-cmh
http://blogs.msdn.com is mesmerising. I can't believe they encourage their developers to post regularly, and that the feeds go out un-edited by management or marketing. Plus, they have anonymous comments enabled.
http://channel9.msdn.com/ is an impressive effort, and shows how far MS is going with their community outreach.
It's scary how much you can learn from blogs.msdn.com. There are a lot of smart people working at MS, but what are they all working on? The quality and thoughtfulness of the posters there indicates that they must have some killer internal projects.
This will dilute "open-source" when applied to news broadcasts and magazine articles which PHBs rely upon. We could explain the intricate differences between "true" open-source and the Microsoftian "shared-source" licenses. But not in a brief sentence. And not in five seconds.
PHBs will just think "open-source is good trend" and "Microsoft 'does' open-source".
So yeah, this is a good, though Machievelian move, by Microsoft.
A NYC lawyer blogs. http://www.chuangblog.com/
MS is just attempting to confuse and dilute the term Open Source.
Microsoft calls it "Shared Source" with a completely different license, not the GPL, and somehow they're trying to confuse and dilute another term called "Open Source?" What's so confusing about it? Couldn't be any more confusing than GPL, LGPL, CPL, XPL, BSD, etc.
Seems rather silly. Especially since Microsoft has been sharing their Windows source with universities for years. In fact, it was a Linux machine at a company called Mainsoft that got hacked which resulted in that Windows source leak. But you didn't see that reported here.
Do you have any legitimate reason for disliking the CPL, other than the fact that MS uses it?
Don't be so antagonistic about topics you clearly have no clue about.
Mathematics is made of 50 percent formulas, 50 percent proofs, and 50 percent imagination.
It wouldn't surprise me.
IE is pretty much worthless to Microsoft, and always has been. They added it to make Windows better, in the fact that it had a browser for anybody who wanted to use it. Now that it's added, it's kinda like Disk Defragmenter. Sure, they COULD improve it loads... but why? It works. Working on it would bring down the wrath of Anti-trust people (Both cases. It would be 'using their market dominance to suppress other companies'). And in neither case would it bring in a single cent of extra revenue.
If they open sourced IE (And, to continue the analogy, Disk Defragmenter), they would gain a legion of coders who would improve the product, making the overall experience better for the end user, and at a far lower cost to themselves. Sure, it wouldn't bring in more revenue, but it'd make the customers happier...
"If we let things terrify us, life will not be worth living."
- Seneca
Erm ... Microsoft is a corporation. Corporations exist to make money and only to make money - the more, the better. There is no such thing as a moral obligation in the eyes of a corporation. They don't do things to "be nice". They do things to make money, or to improve their prospects of making money.
...
So yes, chances are virtually everything they do is devious in one sense or another. But the same goes for IBM, Novell, Sun,
Yes, my only tool is a hammer. And you're starting to look like a nail.
Just which product(s) will be shared source might be of interest to some pundits(I predict IIS being among the first ports on the server side, if it ever happens, simply because there is less server market share to lose there, they're already way behind apache, oracle web server, ibm web server, zeus et al... Windows Media Server is also a candidate, simply because they are licensing it as part of a larger product, but not selling it directly, in a marketspace where the competitors are much more expensive, but offer much more features{real} or are free{apple/darwin streaming server}). On the desktop I have a harder question, is this source thing just an attempt to blindside consumers? They could always say they are open sourcing word viewer after all... Nothing says they have in mind to open the source of a product that actually reads a specific Microsoft format, or that said product has to be unencumbered(patent-wise). Microsoft has always been a master of the "give with one hand take away with the other" I predict more of the same, just where is my only question. Let's not get carried away at least until they have named those products, and listed their intent as regards to data formats et al contained in there.
Why is this important you ask? Well let me put a hypothetical case:
1) you have the source code to office
2) the office file format is encumbered
3) you use the source code to do anything with regards to that file format(read, write, export, clean up, syntax-highlight it doesn't matter)
4) you are in violation of their patent, and can(and likely will) be dragged before a court
It doesn't matter that they opened up their source in this case. Should anyone who hasn't been following, that means that open source benefits end users most when linked to open formats. What this smells like to me, is a PR move related to stock valuation, they announced they would follow the trend, but without naming the products, to gauge the impact on stock price, and they are evaluating which product will be released, based partly on market reactions. If their focus groups say "bad juju" they'll pull up something like ms dos 2.11 or microsoft notepad, and claim they open-sourced it to encourage innovation in the text space
[sarcasm]implying that they are leaders in the text-only field[/sarcasm]
There are a lot of technologies that Microsoft started, like WMI, that would actually benefit from an influx of third party developers, actually, the number of technologies at Microsoft that wouldn't grow with an influx of third parties is actually pretty close to zero.
However, if we want our computing to be unfettered, we have to keep insisting on what's really important, and not be swayed by Microsoft's "No" "No" "Maybe" "Yes but only if you give me the Moon first" routine. The data on our computers, belongs to us, the computers, they also belong to us, the software on it provides a useful service, it is true, but it does NOT grant control to Microsoft over that, and we need to react forcefully to anything that lessens our control over our property.
Maybe you should look at this there cowboy. Doesn't look like Microsoft is exactly wanting to be as open as you think...
Even better, we can find out what all those BSOD messages are.
Sample Code is released to show how to use APIs. It is open source in the sense that you download and modify the source code, but the build isn't useful for distributing in its own right, unlike a TRUE Open Source project.
True Open Source projects tend to be portable between platforms. Many projects on SourceForge can be built on Win32, Linux and Mac OS X.
But what can Windows Template Library (WTL) and Windows Installer XML (WiX) be built on?
My perception is that Microsoft's open source initiatives are simply a means of encouraging use of the Windows platform. They're making available source code to show how certain things can be done, thus giving developers an example of how routines should be written, but also meaning that these "open source" offerings are little more than extended sample code that you expect to get with a Visual Studio install.
I worked at Microsoft until sometime last year. I wasn't in a great or glamorous position as a developer or anything. But working there did make me pay attention to the policies to a greater extend than I do now.
.NET which seems to commoditize the OS much like Java....
A number of us in my department (we joked that it was the "armpit of Microsoft," but I forget who coined that phrase), noticed that Microsoft seemed to be pursuing greatly differnet and conflicting strategies relating to the saturation of the PC market and the threat to revenue that this engenders. On one hadn you had software assurance as an attempt to create a stable income source as PC's live increasingly long lives, and on the other you have
This is yet more evidence to me that Microsoft is NOT acting in a unified and coherent manner but us taking a shotgun approach out of fear (interestingly, not fear of Linux, but Linux contributes to an already bad situation).
LedgerSMB: Open source Accounting/ERP
"Name an instance of IIS being automatically exploited. I'll cite you two Apache holes in return."
Here you go, freshly under investigation, spreading as I type.
From the article: "Government and industry experts warned late Thursday of a mysterious, large-scale Internet attack against thousands of popular Web sites. The virus-like infection tries to implant hacker software onto the computers of all Web site visitors. [ ... ] The mysterious infection appeared to target at least one recent version of software by Microsoft Corp. to operate Web sites, called its Internet Information Server, popular among businesses and organizations."
That was fun. Your turn.
When contemplating such an action one should keep in mind that anything that Microsoft does is pro-monopoly, screw the world encapsulated.
I use the KISS formula...
There are a lot of naive comments on this news story. Microsoft's goal is to keep, exploit, and extend its monopoly, by whatever means (and exploiting its existing monopoly to extend monopoly power to additional areas is inherently illegal, so Microsoft is a criminal organization). This open-source release is a tactical move. It tells nothing about Microsoft's real goals.
It was probably justified within Microsoft on grounds like the following: (1) it will distract some of the Open Source community, possibly even con them into working for Microsoft unpaid, (2) it will generate some good publicity.
He used to be the lead guy at Softway Systems, and developed the Interix package that's now the core of Windows Services for UNIX. Interix could also be described as "Microsoft GNU/NT", since it makes extensive use of BSD and GPL source code, including GCC and large chunks of OpenBSD.
He's a smart cookie, and has given multiple presentations at Usenix on Interix. It's based on a modified version of the POSIX subsystem, and runs directly on the NT kernel rather than under the Win32 subsystem.
I wonder if they're considering open-sourcing parts or all of the POSIX subsystem? Heck, even documenting and opening the NT kernel interface without releasing any of the code would be a huge step forward.
I think that what worries Microsoft more than anything else is the saturation of the PC market. Time was when businesses upgraded their computers (and software) every 2 years. Now the hardware is upgraded every 5 years, and the software maybe every 4.
.Net to try to get developers to move to the latest and greatest (unfortunately undermining 1 and 2 above).
Microsoft's biggest and most dangerous competitor is, well, legacy Microsoft software. This is the cudgel which could destroy their current business model. And I think that this is what scares Microsoft so much.
You see-- if only half as many people buy Windows (because they already have a version that works for them), then they will have to charge nearly twice as much for each copy or cut way back on research and development. Both strategies force them into a chicken-and-egg cycle where the costs go up, the demand goes down, so the costs go up, so the demand.....
So what to they do?
1) Product activation (to forestall the cycle a little while)
2) Software Assurance (to stabilize their income)
3)
4) Longhorn DRM to get consumers to move so they can have "must have" content.
5) Outsource technical support to India
Enter Linux. Linux is at best for Microsoft a current distraction from the market problems above but it is important strategically because it prevents Microsoft from using its monopoly power with market impunity. Linux is a small but seriously growing threat, and while it is nowhere near the threat to Microsoft that Windows 98 is, it provides subtle damage because it gives customers a third option (stay where you are, upgrade, or move to Linux). This third option is a major issue for Microsoft and they know that it could eventually be as bad as the first (stay where you are) option. So they are trapped.
Now, I don't believe for a moment that Microsoft will go out of business over this. But they are beginning an extremely difficult transition, and it is anybody's guess what sort of business they will have when they emerge.
LedgerSMB: Open source Accounting/ERP
The media (amongst others) will pick one and then the two terms become one in the same in the eyes of everyone except the geek sector. We end up looking like we're quibbling over the semantics of two things that most people will consider to be identical. For example, "I can see the code, what's the difference?"