While you’re correct, that’s funny because as a developer using a framework like dotNET, MIT gives YOU more freedom. At least for anything statically linked where the GPL code would end up as part of your binary and force you to GPL your own code I believe.
After years of debate about licenses for my own software (that only I use…), my philosophy has been boiled down to this: MIT for libraries. GPL for programs.
This way, other developers can freely use your library, and your program remains free.
While you’re correct, that’s funny because as a developer using a framework like dotNET, MIT gives YOU more freedom. At least for anything statically linked where the GPL code would end up as part of your binary and force you to GPL your own code I believe.
After years of debate about licenses for my own software (that only I use…), my philosophy has been boiled down to this: MIT for libraries. GPL for programs.
This way, other developers can freely use your library, and your program remains free.