Skip to content

Instantly share code, notes, and snippets.

@bradfa
Created September 3, 2013 16:36
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save bradfa/6426296 to your computer and use it in GitHub Desktop.
Save bradfa/6426296 to your computer and use it in GitHub Desktop.
I like the MIT and ISC licenses.  They fit with my desire to not have to jump through hoops to comply with various licenses.  Many companies do this poorly or not at all.  MIT and ISC do keep copyright intact.
For MIT and ISC, it seems compliance would be as easy as putting a copy of the license, compressed or not, into flash memory on an embedded system.  Job done, the license is distributed along with the software.
I do not want to have to comply with the GPL mostly out of laziness.  In a small company, if I'm the one wanting to use GPL code to make my life easier in development then I'm the one who has to make sure the business complies properly.  Even complying with the BSD license means that the product, when sold, must have some documentation included in order to comply.  That's a pain in the butt that many companies don't want to deal with or don't know they need to deal with.
Yes, there's the risk that someone take a project licensed under ISC or MIT and go sell it on their own and not contribute back.  But making a great community around the software will deter that to some extent.  Plus, if someone's going to take the code and fork it and not contribute back, just let them.  The copyright is still intact and you don't need to 
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment