Microsoft Finally Open Sources Windows 7 Tool
Jan writes "Microsoft has
open sourced the Windows 7 USB/DVD Download Tool by releasing it under the GPLv2 license. The code is now available on CodePlex, Microsoft's Open Source software project hosting repository, over at wudt.codeplex.com. The actual installer for the tool is now again available for download at the Microsoft Store (2.59MB). (Microsoft previously took responsiblity for the violation.)"
It's good that Microsoft took responsibility for this, kudos to them.
For a company that believes so strongly in the inviolability of Software licensing, it's nice to see them practice what they preach when it comes to the rights of others. Fair play to Microsoft for meeting it's requirements, and score one for the GPL and Open Source.
So there I was, scribbling down some notes off the PC screen by hand, when I reached for the keyboard and Ctrl-S'd.
You apparently have never worked in a large company before. There were probably 27 meetings before someone high enough up the food chain stuck their neck out to say "ok". We're talking about opensourcing code from a company that generally doesn't do it. Legal was involved, top executives were involved, someone had to talk to PR about spinning a press release, etc etc. This isn't like some dev got emailed and said, "Shit! I better get that posted right away!"
And this post is PROOF that you're a MORON. Microsoft hires the most expensive people. They may outsource some of their coding, but if you think Microsoft writes any "worse" code than anyone else, you're an idiot. It's like you think suddenly because highly paid, highly educated, highly experienced developers start working for a company you irrationally hate that they become bad developers.
The bigger news is not that Microsoft open sourced the tool after their GPL violation (that was inevitable). The news here is that Microsoft kept the open source tool instead of replacing it with one of their own. Microsoft has open sourced portions of their code before, that really isn't newsworthy. Keeping an open source tool that will be used to deploy their crown jewel operating system by millions of people - that's newsworthy.
It's been, what, a month since they were informed of the lapse, and less than that since they acknowledged the error?
Show a reasonable amount of patience.
I can't help but notice the "finally" in the title.
Really slashdot, can't you post any MS related story without personal bias?
If what you write is true, the reason there's still buffer overflows in Microsoft code is simply that nobody's asked the programmers to get rid of them. Frankly, I find htat hard to believe.
Good, inexpensive web hosting
filled with hacks like the Big Global Lock that used to be in the Linux kernel
The spinning hourglass begs to differ.
Eh... I understand what you are saying. And yet, Linux has never produced anything nearly as bad as Longhorn. Seriously, Long- freaking-horn. You can't praise them for 2000 and xp SP2 and ignore their obvious mistakes with xp/xp-sp1 and longhorn/vista. Every version of windows that is released is accompanied by a story interviewing some Microsoft fellow that describes how bad the source code for the previous version was and how no one really knows how all of the different parts of windows interact. I'm sure its not bad code full of obvious hackery and bad coding. I am however convinced that its a more difficult of a design than the Unix philosophy and it suffers because of that.
Plus, as closed source we can just sort of imagine the code that causes the problems we run into, where as with linux we can actually see the code that caused the problem so we don't have to imagine any code crappier than what we find.
Well.. maybe. Or Maybe not. But Definitely not sort of.
Anyway, trust me - it's very professional, clean code, nice design, and not filled with hacks like the Big Global Lock that used to be in the Linux kernel.
Bad example. Just about every uniprocessor-developed OS had a Big Global Lock until they went multi-cpu - and even then it usually took a few releases before it was really eliminated. I would be hugely surprised to find that the Win9x series didn't have one too. When did the linux kernel deprecate it? Like a decade ago?
When information is power, privacy is freedom.
This third party code would have been produced under contract as "work for hire". Presumably, the contract stated that the third party had to assign all rights to the code to Microsoft, like any other work for hire, and that the end product must be wholly assignable.
Most likely, the third party actually violated their contract with Microsoft by creating a work that uses GPLed code.
There is no "-1 offended" or "-1 you don't agree with me" mod options for a reason.
I'm sure its very pretty. But at the end of the day, it doesn't work as well as the Linux kernel.
Obviously you haven't experienced the joy related to binary Linux drivers (WIFI and 3D come to mind). Let me guess you're doing studio audio production on Linux because of the low latency performance?
Linux makes for an awesome hackable server and it is very flexible. The tools available for networking and development stand on their own but the awesome begins to fade after that. If only BeOS had lived (yes I've been following HaikuOS)...
Man blir trött av att gå och göra ingenting.
Linux audio. Just... Linux audio.
---
Most of the senior engineers at the time were working on Windows Server 2003. The people working on Longhorn were less experienced, and after a bit they started to put their pet projects into Windows, similar to the Copland fiasco Apple went through. (The difference was probably pride rather than fear of getting fired, like "see that? That's my idea!", but meh.)
Jim Allchin wrote his "I'd buy a Mac" memo here.
After they shipped Server 2003, they tried to clean up the Longhorn mess - first by cutting out some of the projects, then by stripping it down and then building up to Server 2003-level. Only then did they decide it was too unworkable, and decided to rebuild straight from the Server 2003 codebase.
Not trying to refute anything here, just giving some background info. Yeah, they definitely could have done a lot better, but they also could have done worse, and I'm not sure that open source would have helped them at all.