the GPL and "development" versus "distribution"
The following paraphrased argument is extremely common:
I’m not against Open Source, I’m against the GPL. I’m against the GPL because it doesn’t give the developer the freedom that the MIT or BSD licenses offer. Copyleft restricts the right of developers.
To develop software means to make changes to your software and expect those changes to run as expected. The GPL, MIT, and BSD license all allow this to happen. All Free Software and Open Source licenses allow this to happen. What the proponents of the above view want to make-believe is that to be a “developer” can simply mean to re-license and distribute code - a task any semi-determined dimwit can accomplish. The mistake (whether through ignorance or an effort to confuse others) made is to make synonymous the act of licensing/distributing with developing.
So when a developer complains that his “freedom” (they like to use this word in an attempt to manufacture a copyleft “hypocrisy”) is obstructed by the GPL, point out to him that it is not his freedom to develop that is obstructed but rather, his privilege to distribute in a way that restricts others. A subtle but enormous difference.
Similar entries
- Thomas Vander Stichele: free clocks
- What in the World?
- Sharing the love
- Free Software: not so 'Free' after all?
- The True Meaning Behind "Free Software"
- Where open source philosophy goes wrong software freedom keeps us free to share and modify
- Open Source versus Free Software from a Marketing Perspective
- OpenAppStore - Do we need one?
- Cultural Significance of Free Software: Two Bits
- Proof Microsoft still does not “get open source”

