Casual use of GPL may be harmful to your health
I’m writing this post using MarsEdit, a well-designed blog client maintained by Daniel Jalkut of Red Sweater Software. Daniel recently wrote a very thoughtful note about software licensing:
Violating the GPL is easy. All you have to do is write some code, intermingle it with some GPL code, distribute a changed copy of the original, and refuse to share your contributions. Bam! You’re toast.
Many developers nonchalantly include code in their applications without carefully checking which license the code comes attached with. Daniel also writes about how GPL might stifle participation:
GPL communities are open and embracing of other GPL developers, but generally off-putting to liberal-license and closed-license developers. Only the liberal-license communities are attractive to developers from all 3 camps.
I agree. Truly free licenses, like the MIT license and the BSD license, don’t limit your freedom or require you to give away the fruits of your labor. Of course, GPL has seen tremendous success and popularity, but in my own projects (both as an open source consumer and contributor) I will choose a less restrictive license whenever possible.