3 ms·
One quibble with using the GPL: it is the position of the FSF that it and the Apple App store licensing terms are incompatible: http://www.fsf.org/blogs/licensi
by hga 16y ago
One quibble with using the GPL: it is the position of the FSF that it and the Apple App store licensing terms are incompatible: http://www.fsf.org/blogs/licensing/more-about-the-app-store-gpl-enforcement http://www.fsf.org/blogs/licensing/more-about-the-app-store-...
However, if you're holding the license, it's up to you if you take action against anyone using your code in an iOS app. (And perhaps you don't want people going down that dark path anyway...).
The more you care about other people using your code, the less you'll want to use a restrictive license. The vast majority of open source Lisp implementations are not GPLed, I assume at least in part for that reason (CLisp was coerced into the GPL by its use of readline). For Clojure Rich Hickey uses the Eclipse Public License -v 1.0 for reasons that I forget but that made complete sense to me when I reviewed them (http://opensource.org/licenses/eclipse-1.0.php http://opensource.org/licenses/eclipse-1.0.php). Do pick one of the most common, license proliferation is a bane of FOSS.
On the other hand, software like language implementations that don't require including so much of themselves in a released version are very natural fits for the GPL, e.g. GCC. The more community involvement you get, the better.