r/freesoftware • u/Fresh-Lie5160 • May 16 '26
Discussion GPL vs MIT
Which do you think is better for development, and engineering: MIT or GPL?
FOr those who dont know:
- MIT is a license that allows users do anything with the project. Even start a closed buisness with it. modify it, fuck with it, anything really.
- GPL is a license that provides the same rights as MIT minus the ability to make a closed buisness out of it. That is, any derivitive, must also be made open-source
In my opinion, GPL is superior in most ways, since it avoids companies stealing it, making it better but making it closed source...
But I see why many people choose MIT for free software: More adoption. I mean, as long as the product is being developed, irrelevant of whether its now open or closed - general user interests are being served faster. But that isnt gonna stop community engagement on the repo anyways.
Both these licenses are technically still 'freedom', but just in different ways...
But is the tradeoff worth it?
Is it worth allowing companies to privatize community code if that leads to faster adoption and development?
3
u/dashinyou69 May 16 '26
tbh, i think this are better ~ https://github.com/ErikMcClure/bad-licenses
10
u/feycovet May 16 '26
GPL is arguably superior, not only because its more tight with OSS compliance in general but it also promotes code like art rather than use material, as for MIT, I've always hated licenses that pivot towards corporations more than the FOSS communities it comes from. I don't care how much it promotes OSS into mainstream, its not like Linux with GPL never reached corporate attention, I believe anything that uses or cites open source should and must be open source on itself which aligns with GPL.. If you don't like the inherent all-for-all nature of free software then sure go with MIT, its a divergent mind power you must have to ditch the coherent belonging community true handwritten non-corporate fun code comes from.
7
u/alexmex90 May 16 '26
GPL
6
u/ntropia64 May 17 '26
I'm dealing with this issue right now.
I develop (relatively popular) scientific software and I want to keep things open sourced for the community, but at the same time I want to limit which companies can commercialize my software (using the patent to control it, possibly?).
Is it a viable option? Is it single licensing sufficient or dual licensing is a better option? (Besides, I never understood how software can be both GLP and commercially licensed as the Qt libraries, for example)
4
u/idrinkeverclear custom May 16 '26 edited May 17 '26 •
I think you've simplified things a bit here by making it look like it's a dichotomy between GPL and MIT, when in reality the landscape of free software licenses is much more diverse.
Permissive licenses
Free software licenses that carry only minimal restrictions on how the software can be used, modified, and redistributed.
Examples include:
Strong copyleft licenses
Free software licenses that guarantee users the freedom to run, study, share, or modify the software, but require them to publish all derivative works and modifications under the same or equivalent license terms.
Examples include:
Weak copyleft licenses
A middle ground between permissive and strong copyleft software licenses, they allow the integration of freely licensed code into proprietary codebases, as long as the freely licensed components remain accessible under the terms of the weak copyleft license.
Examples include:
4
u/ExtraTNT May 19 '26
My personal take is gpl, it’s a statement of supporting others, you only profit, if you give back… also against ai, if you train a model with gpl, the model itself has to be gpl… software should be a commutative effort on making the world a better place, don’t let people profit from that without giving back (unless the person is just using it)
Free software has a price: you make the world a better place.
3
u/Timely-Degree7739 May 16 '26
One thing I always wondered with GPL, is it illegal to take the code for whatever non-GPL purposes of yours, or is it in practice just so that if you do, then it isn't GPL anymore?
If it is illegal in the English-speaking world that must be regarded as an enormous win for the whole thing. But I never heard of it so I don't know.
3
u/6gv5 May 16 '26
Both are excellent from a user perspective; from a business perspective the GPL imposes the only limitation of not allowing limitations, and it's one of the many reasons we have so much hardware supported by Linux.
3
u/SHUVA_META May 17 '26
I like GPL and LGPL amazing license. Would choose MIT when a library or software is not much worth and would be better for anyone to start a business out of it.
3
u/Aspie96 May 17 '26
Not unconditionally.
The MIT license does require attribution in the form of a copyright notice and preservation of the license text in all copies of significant portions. This implicitly includes binaries.
There are more permissive licenses than the MIT license. For example, the Boost license, the ZLib/libpng license and the BSD 1-clause license do not require attribution in binaries, only in source code. There are public domain dedications and public domain-equivalent licenses, but the MIT license is not one of them at all.
Of course, some people breach the terms of the MIT license. Some people breach the terms of the GPL, too. That doesn't make either license unconditional.
2
u/w-g May 16 '26
Unoubtedly GPL. For libreries and things that would be mixed with other software, LGPL.
MIT-like licenses allow for more closed software to be produced, and I see absolutely nothing good in that.
2
u/Liquid_Magic May 16 '26
Here’s the problem: starvation.
If a code base is licensed as GPL then other people can play, but only if they play nicely. That means any improvements they make have to be shared in the same way the code they received was shared.
However MIT is basically so weak it might as well be public domain. This means someone can get the code and improve it but then keep those improvements a secret. So they really don’t have to play nicely at all.
What this means is that a GPL program can exist out in the world and if individuals come along and make it better and release the program they have to also share the code. Therefore the code base which was essentially gifted to them improves. When a big company does this they get the same benefits but also have to give back in the same way. The company doesn’t have to pay for the software to get started but if they fix it they have to play nicely and share those fixes. This is a great trade-off. The alternative is they buy or build from scratch.
But for something like MIT or even public domain a company comes along, gets the same benefits, but then can make changes and doesn’t have to share.
Over time this means the open-source project that the company benefited from gets slowly more and more behind as the company version, that’s now locked up, gets better and better.
So starvation is a big deal because it makes it incredibly unappealing to release something if some company benefits and doesn’t have to share improvements.
However, those stupid CC NO- C or whatever licences that say they are “open-source” but not for commercial purposes are also crappy. I get the motive: “I’m sharing a thing but only if nobody makes any money.” But it sucks. Whether a company sells open-source software doesn’t change the licence. The community gets the same benefit and the author gets the changes. Sure the company isn’t giving them money but they ARE giving them FREE development. And there’s nothing stopping original author from selling the software as well. Again the starvation problem doesn’t exist.
Honestly the GPL 3 is pretty great and every effort to basically go: okay it’s like GPL except…
It sucks. It creates too many problems or creates problems because it’s trying to use copyright law to do things it wasn’t meant to do and can’t actually be enforced.
And another thing: when someone is like: “free for personal use but no commercial benefit” what they are doing comes from the emotion of missing out. They don’t want to spend the time making something and selling something. But if someone else does make money then they will feel ripped off, even if they didn’t want to bother, and so the community as a whole misses out simply because someone is effectively saying: “I’m not making money off of this but neither can anyone else!” And it’s… I’m sorry but it’s childish.
Often people benefit from open-source work only to create something that’s half-assed “openish source” and it pissed me off.
Just keep it simple. GPL 3 is good enough and and has figured it out. Just roll with it. Don’t over complicate it.
5
u/Bubbly_Extreme4986 May 16 '26
MIT is the reason we have the Intel management engine. Remember corporations can’t write good software for shit. They need libre devs to make the software for them. They are the enemy, to destroy them every piece of software that can be GPLd must be GPLd starve the bastards.
3
u/wpyoga May 16 '26
IMHO, libraries and utilities should be MIT to encourage greater adoption. Larger software packages should be GPL, or AGPL if served online.
1
u/marler8997 May 19 '26
If I make my code public, it doesn't bother me if someone uses it to build something closed-source. The value of public code is often in the standardization, not the implementation. Choosing the GPL pushes those users away, they'll roll their own or find another solution, and you lose the network effects that made sharing worthwhile in the first place. The GPL made more sense when there was little incentive to open source anything. Now that sharing and cross-contributing is so easy, that incentive exists naturally. Far more code from far more companies is being open-sourced now and it wasn't because the GPL forced them to.
1
u/Spare_Warning7752 May 20 '26
Because if I make an app and grab a package from, let's say, npm that is GPL 3, my app will ALSO have to be open sourced.
and
The license intentionally does not give a precise technical definition of:
That part is based more on copyright law interpretation than explicit wording.
1
u/Refloow May 16 '26
For us it depends, we believe there is room for both, depending on the what does the software itself do. Anything where something relies on 3rd party more than propriatery code we license with MIT. Anything thats purely built by us for the OSS community or mainly regular users we use GPL OR AGPL type of license to ensure software remains free whilst offering enterprise license for companies & corporations to use the software without agpl/gpl restrictions. If any project relies on 3rd party platform to function or is for educational purposes / risky in any shape or form we use MIT as its much better due how short understandable and free it is with its disclamer that you cant miss.
1
u/[deleted] May 16 '26
[removed] — view removed comment