3 ms·
This is a matter of opinion; like, on the other side of this, one could argue that people who expect to be able to use the works of others without providing any
by saurik 14y ago
This is a matter of opinion; like, on the other side of this, one could argue that people who expect to be able to use the works of others without providing anything in return are being inherently selfish, and that the system should be designed to limit the scope of their damage. In this case, if you'd like to get the functionality of that GPL library for your product, your quid quo pro is going to be the source code of the system you built that relies on it, and which apparently wouldn't exist if you didn't have access to that GPL library.
(Note: if your system could exist without that GPL library, as you could easily reimplement it yourself or use an alternative, then the idea from GPL is "ok, then you go ahead and do that, and we'll keep improving our library, at least knowing that you didn't benefit from it".)
In essence, by having put a library out under BSD, you are simply doing free work for others who are able to take what you did and contribute nothing back; in comparison, using GPL, the people who would have contributed back are not affected, and the people who don't have to look elsewhere: it is a restriction that provides a direct benefit.
- notimetorelax 14y agoI respect this point of view and somewhat agree with it, on the other hand I have received great benefit from Apache, BSD, etc. licensed software. So when I contribute to OSS I make sure to use similarly permissive licenses. Yes there will be others who profit from the OSS and don't contribute but I don't think that there's a way to prevent it.