3 ms·
Well, it forces to open source anything "linked together" with the GPL code, even if it has no relation to it and is in no way to derived from it. So in that se
by _ph_ 10y ago
Well, it forces to open source anything "linked together" with the GPL code, even if it has no relation to it and is in no way to derived from it. So in that sense, GPL tries to force the developer to release unrelated code under GPL.
Of course, as a consequence many developers refuse to use any software distributed under the GPL (as in using GPLed code in their software). I am not sure how this is a good thing.
- prodigal_erik 10y agoThe right to include other copylefted code is an incentive to copyleft your code. If a developer is shipping proprietary code instead of advancing the profession, I have no interest in helping them, I wish we could tell them to go to the beach and start making their own transistors.
- _ph_ 10y agoNo, it is not an incentive. As I cannot publish my full stack of software, GPL code is just no option for me. And why am I not "advancing the profession" if I open source as much of my code as I can? But for the license technical reasons not as GPL, but rather BSD? Your last wish of "start making their own transistors" is really funny in the context, that some of my proprietary code is actually for making transistors.