Originally Posted by mott555
Microsoft doesn't necessarily "hate" open-source software, they actually have a ton of open-source projects themselves hosted on their CodePlex site. The WPF and Silverlight Control Toolkits are the biggest open-source projects from Microsoft that I have to deal with all the time at work.
I do believe that Microsoft hates the GPL license, and I tend to agree. The problem with GPL is it requires any derivative works to also be GPL-licensed. So if you work for a company and you're building a proprietary software product and you need to find a third-party library to accomplish something, and you find that library and discover it's GPL, now if you want to use that library your company has license the product as GPL and must freely provide its source code to anyone who asks for it and must agree they can use it or modify it for anything they want! Most companies cannot or will not do that for good reason.
it depends on which version of the gpl the library is release under.
if it is released under lgpl, then it can be used in proprietary software and the source is safe and sound.
now it being released under the gpl, that seems to be a point of debate. some think static linking to it, is a derived work, while others believe any linking is derived, and others hold the belief as long as it doesn't change the library or use any "cut and paste" coding from the library, then it isn't either.
courts seem to also be hit and miss on this debate as well, some courts have viewed any use of gpl libraries as being "derived" where others have said there is no evidence that they changed the library in any form, so the work created is not derived, and there for does not have to be released under gpl.
i think MS is taking a misconception about gpl and turning it into a business practice, gpl only states that source code be made available upon request, doesn't say anything about it having to be bundled with a software binary.
but then again i could be wrong about that, as gplv3 is not very popular, you will find a majority of opensource software still licensed or continued to be licensed under gplv2.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
this is taken directly from the gplv3 about "giving out source code", just goes to show that the boys at MS like our "news" readers here don't bother to read the articles or do independent research