Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualHodgman

Posted 08 October 2012 - 07:04 PM

I prefer the BSD license (it's quite similar to the MIT license) than all the GPL stuff. It feels much less constricting somehow. But overall I don't really care, I just pick a license and get on with the code.

+1
GPL/LGPL are too restrictive. I use MIT/BSD-style licenses whenever I release open-source code.
In my closed source games, I always really try to avoid using any 3rd party libraries that are LGPL, because I don't want to have to deal with it's arbitrary decisions on how I must package my binary code... For anyone wanting to license their own work under something restrictive like LGPL instead of something totally free like MIT/BSD, I'd recommend that they instead use the EPL over the LGPL.

#2Hodgman

Posted 08 October 2012 - 07:02 PM

I prefer the BSD license (it's quite similar to the MIT license) than all the GPL stuff. It feels much less constricting somehow. But overall I don't really care, I just pick a license and get on with the code.

+1
GPL/LGPL are too restrictive. I use MIT/BSD-style licenses whenever I release open-source code.
In my closed source games, I always really try to avoid using any 3rd party libraries that are LGPL, because I don't want to have to deal with it's arbitrary decisions on how I must package my binary code...

#1Hodgman

Posted 08 October 2012 - 07:00 PM

I prefer the BSD license (it's quite similar to the MIT license) than all the GPL stuff. It feels much less constricting somehow. But overall I don't really care, I just pick a license and get on with the code.

+1
GPL/LGPL are too restrictive. I use MIT/BSD-style licenses whenever I release open-source code.
In my closed source games, I always really try to avoid using any 3rd party libraries that are LGPL.

PARTNERS