4 ms·
OK, so large companies won't extend your software. What's wrong with that?
by TazeTSchnitzel 11y ago
OK, so large companies won't extend your software. What's wrong with that?
- mhurron 11y agoSome people don't have a problem with that.
- jules 11y agoMaybe you want your software to be used? I wish people could be a bit less religious and moralistic about licenses, especially the GPL camp.
- yarrel 11y agoPeople being less religious and moralistic about use at any cost would also be nice.
- maxlybbert 11y agoThe argument in the article is wrong. The assumption is that companies want to extend the software and keep their extensions "locked down." That does happen, but I have seen companies willing to extend software, and make the extension public, as long as they didn't have to make the extension GPL. Whether this makes sense, or is a case of failure to understand the GPL, it does exist.
- liviu- 11y ago>The argument in the article is wrong. The assumption is that companies want to extend the software and keep their extensions "locked down." I think that's by far the most common use case for avoiding GPL though.
- ubernostrum 11y agoI think that is commonly assumed to be the most common use case for avoiding GPL. I have no idea whether that is actually the most common use case for avoiding GPL, and I don't know of anyone who's actually done the research on that in a useful way.
- TazeTSchnitzel 11y ago> The assumption is that companies want to extend the software and keep their extensions "locked down." That does happen, but I have seen companies willing to extend software, and make the extension public, as long as they didn't have to make the extension GPL. ...so? The point is that the GPL makes it illegal to lock down, while MIT and the like enable it. Yes, some companies will play nice, but they are doing so voluntarily.
- maxlybbert 11y agoThe solution to "companies are evil and want to horde my code" is very different from the solution to "companies don't like the GPL; perhaps because they don't understand it, perhaps because they don't like the implicit patent license that may include any patents the company has a cross license to and doesn't have the ability to sublicense."
- stephengillie 11y agoAt Microsoft (at least circa 2010) you weren't allowed to even install GPL software, for fear that a developer might wind up using it somehow, and cause the GPL to apply to all of, like, Windows 7. Sorry for the hyperbole, but the concern was very real, even if poorly defined.
- FigBug 11y agoThis is such nonsense, using GPL software can't 'infect' software you are writing. I could understand having a rule about not putting GPL source code on your machine in the case you might accidently reuse some of it -- but even that seems unlikely. I guess it's just easier to say 'GPL bad' than actually explain copyright to every developer.
- dalke 11y agoThere were some people at Microsoft using GPL software. For example, Microsoft's Virtual Server 2005 R2 supported Red Hat Enterprise Linux, according to this book from 2007 : https://books.google.com/books?id=BAtUWStlEUwC&pg=PA41&lpg=PA41&dq=linux+at+Microsoft+2005&source=bl&ots=S9TAbGgNvP&sig=w9T3mrrdsCpdhCted65ho_6VEcg&hl=sv&sa=X&ved=0CGkQ6AEwCWoVChMInOTjweLsxgIVYnxyCh14hQyy#v=onepage&q=linux%20at%20Microsoft%202005&f=false https://books.google.com/books?id=BAtUWStlEUwC&pg=PA41&lpg=P... . And http://www.cnet.com/news/microsoft-embraces-gpl-opens-hyper-v-to-linux-with-linuxic/ http://www.cnet.com/news/microsoft-embraces-gpl-opens-hyper-... from 2009 says "Microsoft embraces GPL, opens Hyper-V to Linux with LinuxIC: Redmond is proving that it can compete with open source on open source's terms by licensing LinuxIC under the GPLv2 license." That said, the concern is indeed real, as http://www.zdnet.com/article/microsoft-admits-its-gpl-violation-will-reissue-windows-7-tool-under-open-source-license/ http://www.zdnet.com/article/microsoft-admits-its-gpl-violat... from 2009 shows ("Microsoft admits its GPL violation; will reissue Windows 7 tool under open-source license").
- ethomson 11y agoThis _may_ have been the default, knee-jerk guidance for the Windows team, or part of it, but it was certainly not true for the whole of Microsoft, even back in 2010. In 2010, Microsoft was shipping a handful of cross-platform tools that we built and tested on Unix platforms including Mac and Linux, where it's literally impossible to avoid using GPL software. Today, Microsoft ships even more cross-platform tools (Visual Studio Code) where again, it's required to use GPL tools, and we contribute to others. (I hack on GPL code as part of my job at Microsoft.) Now, of course, you're right that this was much harder within Microsoft five years ago. And one's risk exposure is different depending on the product portfolio you own (with something like Windows being less risk averse than something like Microsoft Bob). But some very key lawyers with their heads screwed on straight have overhauled our system and it's much, much easier to deal with OSS than it was five years ago. But even then it was certainly _possible_ and actively happening in parts of the company.