Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
GPL and MIT are more or less the same to be frank.
I personally prefer GPL because I love GNU/FSF. Implications are pretty much the same.
GPL is a restrictive mess, that will eventually reduce the success of your project, since it restricts its use cases.
Also its much easier to understand than GPL, for proof, just visit https://choosealicense.com and compare the GPLv3 and MIT samples.
I use MIT for pretty much everything I make, simple and permissive. I used GPL before but MIT is less text what means less subtle restrictions.
When I contribute, I use the license of the project. Otherwise, the most projects will not accept the contribution.
GPL is certainly not the same as MIT. I usually use the latter or just no liecense when I'm doing my own thing. Never GPL dear god
Haxk20435584yMIT is basically. Use the code as you wish just don't sue me.
GPL is for projects that you create and are kind of new thing and you don't want people stealing the project to sell it.
I'm using GPL because I don't support closed source leeches.
GPL or MIT License ? What you guys prefer to contribute, use, or whatever on Open Source software?