5 ms·
Common wisdom says to use the best tool for the job. Why wouldn't the same thing apply to licenses? The MIT vs GPL argument seems silly to me. Use whichever one
by bmaupin 7y ago
Common wisdom says to use the best tool for the job. Why wouldn't the same thing apply to licenses? The MIT vs GPL argument seems silly to me. Use whichever one best applies to your situation.
Writing a library and want maximum adoption? Use MIT.
Worried about patents? Use Apache.
Want to ensure the code stays open-source? Use GPL for an application or MPL for a library.
Obviously these are grossly oversimplified examples to make my point. But I wouldn't write a web application in C or a device driver in JavaScript. So why use the same license for all of your code?