Also, would you use the same language to describe typical proprietary licenses? After all, most of those would also prevent me from publishing any codebase incorporating any code I obtained under such a license as free software--or in your terminology, the codebase would be "infected" by the proprietary license which forces my software to also "catch a proprietary license"? I'm not quite sure I understand your analogy, though ...
The GPL does not force software to be free. It is not viral. Please stop using such dishonest language. The GPL will only be a part of software project if you choose to use it. It doesn't invite itself in.
Do you believe that proprietary software licenses are tyrannical as well?
Freedom is all about what you want to do, the problem is that GPL developers and developers who sell things to clients have different objectives for what they want to do. Likewise users of paid for software and users of GPL software have very different expectations of the software, GPL users tend to want to modify the code, and paid for software users want the software to work, but don't want to modify it.
So for a GPL developer GPL code is very free, for a non-GPL developer it's not very free.
Which also seems to highlight a possible confusion on your part, that somehow "paid for software" is the opposite of "GPL software". When I sell software, customers tend to want to be able to modify it, or to have the ability to have others implement modifications for them. And that works both with proprietary code as well as with GPLed code: It's no problem at all to sell code under a proprietary license that allows modifications for own use, but it's also no problem at all to sell code under the GPL, which also allows modifications, and at the same time allows me to build on GPLed code.
Also, I don't think terms such as "GPL developer" make much sense. There just is code out there that you can use under different licenses, some of which are incompatible, and for a given project, you have to take care to select components that are compatible technically as well as legally, both between them and with the requirements of the project--and in particular, there isn't really anything all _that_ special about the GPL, as you cannot include proprietary code in a project when the license is not compatible with the customer's requirements either.
So, you value developer freedom, but not user freedom. Copylefted software is "tyrannical" to you because it prevents you from using the software to build proprietary software.
>GPL users tend to want to modify the code
Well, some of us modify some of the source code. But I use most free software unmodified. Free software isn't merely to satisfy my penchant for hacking, but to give me the freedom to have control over my computing and share with my neighbors.
>paid for software
Free software is about freedom, not price. Software can be both free and "paid for".
For non-GPL developers, GPL code can even be more expensive than the cost of a proprietary library.
I can understand why one would publish under MIT/BSD because they think that a developer is entitled to close source their software even if it builds onto free software.
But then if you support such freedom for the developer why isn't a developer entitled to publish under GPL because its their software and they can do whatever they want with it.
It seems like this viewpoint is implicitly saying that close sourcing the code is totally fine, but publishing the code under GPL isn't. That does not make sense to me.
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.
"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 also really appreciate what morbius wrote in this same thread: https://news.ycombinator.com/item?id=7757677