Re:Why you shouldn't use the Lesser GPL for your next library
by dllthomas on Monday May 19, 2014 @12:01PM
(#7768107)
This is an incorrect understanding of GPLv2. From the GPLv2:
"This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License."
I never said that a developer isn't entitled to their choice of license. In fact, I fully support and encourage that. But choosing GPLv3 and then expecting people to use the library is a conflict of terms. I have equal rights to yours over how I license my code—at least until I pick the GPL. [2] So, attempting to dictate what license I use when writing my code by including a "viral" copy-left clause in your license is tyrannical and arrogant.
I do have to eat. So if my only choices are GPL licensed libraries and a project we can't release source for, all you GPL-only guys make me waste my time writing a proprietary library.
I absolutely resent the copy-left. And I won't ever use the GPL because I won't inflict such terms upon anyone, commercial or open-source users of my libraries or software.
[1]: https://www.gnu.org/licenses/gpl-faq.html#IfLibraryIsGPL
[2]: Bear in mind that my day-job is writing PHP code, and all distribution of libraries and software is in source form. The GPLv3 has special exceptions for statically linked languages loading the library dynamically, but in PHP the whole application is (arguably) in source form and always loaded dynamically.