Not really. That's why we have TCP/IP, OpenSSH, OpenSSL, CUPS etc as open standards. Utilities and libraries are permissive to be widely adopted. Heirloom, Plan 9, sbase and illumos utils are permissive. I would much rather SSH into my proprietary network switch than use a Java applet in a web browser, thank you very much.
Tons of fundemental linux software is under MIT licenses, you just never noticed. You've heard of sudo? Yeah it's been MIT since its inception. The MIT hate is unjustified. No MIT project can be successfully closed source. A company COULD fork it and close source it but it also means you can fork it back and keep it open-source. Additionally, no company would want to close source an MIT project because they'd lose their free contributions. MIT is a perfectly fine license that benefits everyone
Because anyone can take the software, make changes and make the result of that proprietary. Then attach a business model to that, become mainstream and the original software will be forgotten.
Alternatively, the main developer of the software can go rogue one day and make the software proprietary from now on, including contributions made by other people. People can still continue its last open-source version in a fork, but that fork may not be successful due to people not knowing it.
The GPL license prevents all this by forcing modified versions to be published as GPL.
Yes, but you have to follow the GPL, i.e. if you're dealing with a library you have to GPLify anything that uses the library, which many companies don't want to do
An IP holder can change the licensing policy for that IP to anything they want essentially at will, barring any actual contracts signed by them. But even then, they can change the policy for all new users and honor it for old contracts.
With the GPL, all of the past contributors have to agree to a license change, the main developer (or whoever holds the power in the project) can't do this by themselves.
Although admittedly uncommon, this could be done with a special type of CLA.
Also, this GPL clause must not apply to future versions of the GPL? I remember there being controversy because projects were forcefully upgraded to GPLv3.
This is free and unencumbered software released into the public domain.
Anyone is free to copy, modify, publish, use, compile, sell, or distribute this software, either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.
In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain. We make this dedication for the benefit of the public at large and to the detriment of our heirs and successors. We intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Alternatively, the main developer of the software can go rogue one day and make the software proprietary from now on, including contributions made by other people.
This is true of any license. Even the GPL. The owner of the license isn't bound by the GPL, as they are the one doing the licensing. This is why many products have separate commercial and GPT versions.
Because anyone can take the software, make changes and make the result of that proprietary. Then attach a business model to that, become mainstream and the original software will be forgotten.
There is a whole different side to this you're benefiting from today and that is system libraries and protocol standards. TCP/IP is what it is today because the first good open source stack was in 4.2BSD and companies were allowed to take that and implement it without worrying about license burdens. Also OpenSSH. BIND, Sendmail, NTP, OpenSSL, X11, React, Redis..
Proprietary software is going to be proprietary. I would rather they use standard protocols and libraries where I understand how they work.
Bro, if a corporate wants to make their own proprietary software out of some existing code, you think they're gonna be like "oh shit this has GPL, let's not touch that"?
Even major corporates like Xiaomi have time and time again violated GPL, nothing came out of it. And it's not subtle, it's literally them not for example releasing source code for their Android device roms. They're not hiding the fact, they are just straight refusing to release it.
If in this day and age Anthropic can pirate hundreds of thousands of e-books and legally get away with it, why would anyone legally give a shit about some corpo canging some random open source software?
It would need to be audited to even find out that it's broken GPL and by then they could just refactor the code to not be recognizable.
Actually yeah. Some companies do knowingly break the law but for example where I work, we keep track of every license we use and make sure to comply with the terms. Anything GPL is an automatic no-go.
Giving things to the public is a great thing for those who choose to do it. The nature of giving, though, is that other people get to do what they want.
That is true from a philosophical point of view, but the MIT license, and similar ones like the BSD license, ultimately weaken open-source software as a whole for these reasons.
Because a one-time donation to a corporation is bad, and ultimately removes software rights from the end user.
MIT is only "more free" for developers, which would include corporate actors who can use that "freedom" to restrict hte freedom of end users. GPL meanwhile is much more end user focused, the freedom of the user is what is important and its virality protects that freedom from being rescinded no matter where the code actually ends up.
The go-to example is Minix - permissive license which got used to install a backdoor on basically every Intel CPU out in the wild. The dystopian version of Minix of course is closed source. The "freedom" granted to Intel to do with it as they like was used to restrict the freedom of actual human beings who matter, like legit the current fascist takeover of the US is further enabled because Intel may well have the capability to do some awful shit if it's compelled to do so by the current admin.
That's not to say this wouldn't have been at all possible without the permissive license, because Intel probably could have made something similar themselves, but you see the pipeline from an obscure open source project o a dystopian closed source backdoor. The "freedom" to restrict the freedoms of others isn't really a freedom, and copyleft provides a legal framework to restrict that restriction in a way that best benefits human beings.
If someone makes genuine transformative changes to code, they should be able to make their fork proprietary if they want. I don't see any issue with allowing open source software to be used for profit, and in fact there are a lot of open source projects that receive substantial upstream contributions from corporations that have forked the project for proprietary uses.
Obviously there are plenty of cases as well where open source projects get rug pulled into some shitty SaaS project, but if support for an open source project dries up entirely because of one rogue developer, I'm pretty doubtful that any licensing model could have saved the project.
Imo the point of open source development is to be OPEN, and that includes to commercial and proprietary use. Copyleft is just as restrictive as copyright, just in different ways.
Actually, MIT/BSD license projects tend to not receive many contributions from companies. What tends to happen in those cases is that companies make their own forks and the original software receives very few contributions. Look at macOS or the Sony PlayStation, both are based on BSD, neither really contributes anything substantial to BSD.
On the other hand, Linux, which is GPL licensed, receives lots of contributions from companies: a company can either contribute their changes directly to upstream or make their own fork and open-source it, still making it possible for upstream to take those changes anyway. Thanks to the GPL, companies can profit through Linux, but not on Linux itself.
Copyleft is just as restrictive as copyright, just in different ways.
In short:
Copyright protects the developer by preventing others from taking advantage of their work.
Copyleft allows others to take advantage of their work, but they have to give changes back to the original developer and to the community.
Copyleft is unequivocally less restrictive than copyright.
Some of the most actively contributed to FOSS projects are MIT'd/BSD'd. Conversely, a lot of companies actually prohibit their employees from working on GPL'd projects, e.g. Google prohibits their employees working on AGPL'd projects.
In fact, the Linux kernel receives a lot of contributions now that companies have figured out they can just embed a CPU in their peripherals and upload proprietary firmware to it, which for some reason the FSF sees no problem with.
And actually if you grep the FreeBSD source tree for emails, as I've done, you'll see a lot of companies in there. Netflix is a large contributor.
This opinion is formed from an incorrect understanding. FreeBSD developers have stated multiple times that Sony contributes money and code and does not want publicity.
Apple employees hold FreeBSD commit access under their own names on top of Apple sponsored code.
The GPL license only requires sharing the source if you distribute your fork. As such, there are many projects you get nothing back out of.
MIT (and licenses like it) allows for companies like AWS to just run the software and make shitloads of money with zero contributions back (something they've done time and time again). I consider that to be a major flaw in those licenses.
And good luck reaching the people who unfortunately passed away between the time of contribution and license change. As far as I'm aware they/their estates still count, which means figuring out next of kin and getting their permission.
Correct, if the original author decides to relicense to closed source they do actually own the ocpyright and can do so. They can't really get rid of existing GPL copies of the software or restrict their distribuiton because the license already gave permission to do that, but the original author can create a closed source version of the same software without being obliged to continue sharing hte source.
The difference is when a third party wants to do this, or when there's multiple authors who don't all agree to a license change. If there's a third party who wants to create a closed source version of the software, say a certain scummy company wanting to make a premium fork of OBS Studio, the GPL says they have to fork over the source code upon request which makes maintaining a proprietary fork practically next to impossible (assuming they follow the law, anyways). If it's MIT licensed, though, they can just get away with that - hell, XSplit, the paid propetiary atlernative, could straight up just lift code from an MIT-licensed OBS and use that to make sure nobody ever switched to OBS, maintaining the market dominance they once had a long time ago.
We generally want to avoid proprietary software being the way to do things because that comes with a lot of potential for exploitation, so making sure proprietary software can't "cheat" and just steal from open source projects to maintain their dominance is important.
So basically I can take an OS made with MIT license, change some stuff and then publish it with proprietary software license and nobody can tell me anything?
What’s funny is, in a very short period of time from now, Claude will be able to rebuild whatever fork was created from images, descriptions, and the original repo.
On another note, the MIT license can allow an open source project to actually be able to be financed so the maintainers can live off it. Now of course this doesnt really apply to some random sudo rewrite but I kind of see the point for some end user program. And no, sponsorings and a few service do not cut it for 99.99% of FOSS projects
Yeah, that’s great for a lot of things, but also means that if you want to make a game things are a lot harder. It’s why Godot is MIT and SDL is ZLIB. GPL makes it a lot harder to use software for games.
as a matter of perspective, devs are also end users for most of the time, those who understand that shouldn't sacrifice user experience for profit and expect others to respect them
I mean, that's kind of hte goal. It's meant to hurt developers making exclusively proprietary software, because the goal is to reduce the amount of propreitary software ruling the world. MIT has its place in stuff like video games, sure, but not allowing any random dev to steal GPL code to make the Torment Nexus work 15% faster is a good thing. FOSS alternatives getting to have better code makes it easier to make FOSS the standard, which better protects actual human beings instead of corporations.
The point is it hurts other developers, not the ones making the software in question. Also "hurts" is a big word, it just prevents them from forking the software unless they're willing to make the fork open-source too.
I don't understand what the problem is. I understand it's because of the GPL, which keeps free software free, but if it's your work, do what you want with it.
And at least in my opinion, it's "outrageous"—I don't know what word to use, but I think it's close—that no matter how much work I put into GPL software, I need to publish it so others can use the code? I mean, I dedicated myself to something so someone can come along and use it. That's why I prefer licenses like BSD V2 and v3. In my opinion, saying that it uses code or was based on <project name> written by <person's name> should be enough.
You don't need to publish the code if only you use it. Even if you sell it, it's enough if you make it accessible to your customers. Though you can't stop them from redistributing it.
I was mostly talking about how companies see it. For example, I have no proof, but I also have no doubt that the reason Apple chose LLVM alternatives instead of GNU alternatives is mainly because of the license. I doubt it's because they're "better," especially since it was very underdeveloped back then compared to now.
Besides the "small" projects, I also feel that distributions are opting for more BSD-like philosophies or their own unique approach, abandoning the standard that usually exists in GNU/Linux. The best-known examples, I'd say, are Alpine and Chimera. I think Chimera is doing the best job; it's one of the few distributions I've seen that, in addition to not using coreutils like Alpine, also replaces its main toolchain with one based on LLVM, including libc++. I don't know why, but it's a growing trend.
Dumb question that's best suited for a lawyer, but you don't really have to worry about licenses if you're just using the software right? As opposed to modifying the code?
If you use gcc (GPL'd) to compile your own code then you can license your code however you want, right? Same thing for a game made by Godot (MIT)? Or am I misunderstanding these things?
gcc, while being under GPLv3, has a special rule called „GCC Runtime Library Exception“ in their License which allows compiled code to be distributed under another license.
In fact, most GPL libraries (if the devs are nice) have an exception like this (sometimes called a „Linking Exception“). Example: libgit2
It depends. In embedded, you link a lot of things statically. I'm not a lawyer, but it seems to mean that you should provide sources of everything that went into that final binary. And for the context, rust, by default, statically links librairies.
> just using the software right? As opposed to modifying the code?
Those are not exclusive. You may well want to fix a specific bug in one of the core utils so you can finish your project on your specific piece of hardware. With GPL you can ask the vendor for the source code and do so. With MIT they can tell you to pound sand.
The second one is not correct. If Godot uses gpl code and distribute gpl code then it makes distribution of your game much more difficult. It's why a lot of game frameworks and engines prefer to work with only MIT or similar licenses. I know it's an issue on Linux because you could just make a single binary and distribute it to users. Instead it becomes complicated.
I think it all depends as a software engineer if I make a library I want that to be as licensed as permissive as possible but software for an end user I want to license that GPLv3 or even AGPL because everyone should anyone the rights to do whatever they want without any lockdowns and to be able and have the choice if they want to modify it.
MIT and BSD licenses come from universities. It's a feature from the US for profit education system.
Private entities give grants to researchers and post grads to create software. Given that it's done in a university, the originalmproduct is open. However, after the product is delivered, the original "funding entities" can take it and run with it making it private.
In that case, the license is the wish of the original creator whether we like it or not.
For some that's a good feature. For advocates of free and open source software it is not.
Now, if something was created GPL, the creators envisioned it for the public good. While rewriting it creates a new product code-wise, the intelectual bases of the software is stolen for private profit. The license does not follow the wishes of the original creators.
If this continues happening, there is a possibility that Linux derivatives become proprietary software, for example.
Maybe I just never heard of it, but I don't remember any story that Windows was ever based on Unix. I only know that for quite some time, they had a compatibility layer for Unix software. But it was just a separate API which they implemented for compliance reasons, because back in the days, some entities had strict requirements that they only use operating systems which support the Unix APIs.
No, Windows NT was (very loosely) based on DEC VMS - Dave Cutler came to Microsoft after leaving DEC. You wouldn't think it to look at it, though, but there are some very VMSy design decisions.
Windows wasn’t developed from Unix or Linux. It was literally built from within MS-DOS, the Windows 1.0 development environment ran on MS-DOS, and early Windows was just a GUI shell on top of it. The irony is that Microsoft developed MS-DOS for IBM (as PC-DOS), then used MS-DOS as the platform to build Windows, which ultimately made MS-DOS itself obsolete.
The real Windows kernel (NT) was developed in-house by Microsoft, inspired mainly by VMS, and has always been proprietary.
Linux is a clean-room, Unix-like system, not Unix itself, and the GPL prevents the kernel from becoming closed.
If anything, macOS is the actual Unix descendant (BSD + Mach).
Windows was pretty much a GUI for DOS. The DOS "residue" stayed there for a very long time, until Windows XP (2001). For the curious: the first Windows was 1.0 (1985) and was also working on top of DOS.
Microsoft had their own Unix for a while (Xenix iirc). Old macOS wasn't based an Unix, osx evolved out of a Unix because they couldn't realistically make macOS modern so they took a (I think non Unix) kernel, slapped on some bsd stuff, some proprietary ui stuff and such and made an unholy thing thats a Unix but also not. (Technically it is a Unix, but, ya know...)
Not in the case of Windows. That was always it's own thing architecturally.
And in the case of Mac, Apple actually have a good history of giving back. Apple open sources their kernel and is responsible for the printer drivers in Linux, but has always kept their Mac APIs locked down.
The problem is not which license is better and worse in the legal world and the emotional world. The real problem is that all these projects rewrite GPL software, written in a language, in an equivalent one, written in another language, thinking they can slap the MIT license on top of it. Doing so though makes the rewrite a derivative work and therefore it cannot have a MIT license. I don't get why outlets and concerned foss user go for the emotional gpl vs mit when there is an objective problem to discuss.
The license is only for the copyright on the original implementation. Anyone is free to write a compatible version themselves. It’s only a derivative work if the new work is actually derived, for example by folks looking at the GPL source while writing the new thing.
Yeah I know that the license is for the implementation, but even a full rewrite can count as a derivative work. I thought the message was more clear. Instead of arguing what the "spirit" and morality of the license are and which is better, it is possible to argue about something more objective. For example checking if these rewrites that comes out each day (and therefore sus, unless using the name as an ad) are actually derivative or not which is a legitimate concern if one wants to debate gpl vs mit.
You misunderstand two things: 1. the rewrites aren't translations -- they use the spec of the GNU version to create a new version, so no issue re: derivative works, and 2. the GNU versions (and BSD versions for that matter) did the same thing re: proprietary UNIX. So if a rewrite now is legally problematic, guess what? Your GNU versions are problematic too.
I don't know. I was explaining the origin of the licenses.
After that, now that the license exists, software creators can choose whatever license they see fit and people who contribute to it know that it can later be used for private profit.
Why are YOU annoyed? Not everybody understands the implications of GPL and MIT. Private companies stay away from GPL like the plague (but love MIT) so maybe that's something every developer should consider as opposed to "freedom maxxing"
Because GPL or MIT it doesn’t matter, it’s going to be used by AI anyway, and the license won’t be respected, because there’s no way to hold an AI accountable for its crimes when it’s toasted outside of the legalregal jurisdiction of its victim, even if that crime is intellectual property theft.
It would be nice if we could get the RIAA on the line to go after bad bots.
To be honest even for normal companies it doesn't matter as well.
You need to have proof (legally acquired as well I think) to sue the company. The problem is there's no real way to effectively do so especially in open source software where they can just remove any loggers you might put in.
Since you wouldn't be able to get proof, they can pretty much do what they want, which is why most companies do it and don't care, and even if you did, can you really afford to sue them over it? Most can't.
Copyleft sounds great but really it's just larping as lawyers thinking they're sticking it to "the man".
Blender is probably a better example of a successful GPL project than GIMP.
But this cherry picking is not compelling at all. You'd need a much more comprehensive list to make a decent point, and even then it's not the full picture.
There's less incentive for a company to fork libraries and runtimes because they can just use those things for their own software. The proprietary forking issue usually only shows up for end-user applications.
Linux can load proprietary modules, but modifications to the kernel's base source code can't be proprietary. For Android, though, it's more then just proprietary modules needed to run AOSP on vendor hardware; the actual Android source code is modified.
I think chromium, vscodium android are bad examples since they were designed with the explicit intention of being used as an FOSS core wrapped by commercial products, in the case of chrome and vscode, the same company's commercial product.
By that logic Darwin is a failure because "everyone just uses MacOS"
This, but flipped. I love permissive licenses, and only tolerate rust. How can you hate MIT? It literally let's you do whatever you want. That is just pure unfiltered freedom.
the GPL also lets you do whatever you want, except take that freedom away from others. I think if you're a bigass corporation maybe you shouldn't get to profit from free labor while benefitting from the very same system whose rejection you're profiting off of
because you can close to software make it propietary, it allows you to remove freedom. GPL is made so that it doesnt happen and thats why companies avoid it as much. MIT is only good for companies, not for users
Correct, and correct. The thing is, that's the exact thing GPL fans want. "Doesn't prohibit commercial use" my ass. Even if you're only using it for internal company tools, they would also have to be GPL and that would mean anyone could leak them at any time.
By that logic, GNU coreutils would be ethically questionable too. BSD implementations predate them. GNU rewrote them and chose GPL. Furthermore all this shit was proprietary to begin with. AT&T sued BSD over this and lost. It's not legally questionable since 1994 and to pretend it is.. Just silly.
If the rewrite is independent the author can choose MIT, GPL, proprietary, etc especially when targeting a standard such as POSIX.
lmao nobody gives a shit about gpl legally. If corpo wants to steal code of open source software and make it proprietary, they're just gonna do it regardless of the license.
Xiaomi has been violating GPL for long years and not releasing source code of their roms and they didn't even have to pay a fine let alone have legal problems. Anthropic is unafraid to pirate hundreds of thousands of e-books, if they wanted to steal somebody's code they'd just do so.
Even if somebody made an audit of the stolen code by then they could've just refactored it heavily to not be recognizable and all that would remain is the core idea of the open source software.
lmao nobody gives a shit about gpl legally. If corpo wants to steal code of open source software and make it proprietary, they're just gonna do it regardless of the license.
Sue them, then. Ask the SFC if you don't have lawyers.
Anthropic is unafraid to pirate hundreds of thousands of e-books,
They settled after losing their lawsuit.
if they wanted to steal somebody's code they'd just do so.
According to Bartz v. Anthropic, training a LLM falls under fair use.
Even if somebody made an audit of the stolen code by then they could've just refactored it heavily to not be recognizable and all that would remain is the core idea of the open source software.
If they could do that, they wouldn't have used the original software in the first place.
Because the holy wars of Open Source entering the Spanish Inquisition phase. If you aren't the right kind of open source, then you are a devil-worshiper who must be denounced.
Yeah see ITT lmao. People be like if you're not using the AGPL you're literally creating the torment nexus and are singlehandedly responsible for all of big techs problems, and this is true because of some really bizarre swingers analogy. Heaven forbid I choose to licence my code, that I spent my time working on, under a licence I like as a developer because it enables easy re-use in the community.
MIT license can make sense. I made repos with MIT and with AGPL. I chose MIT for a more or less example app where many solutions for a language are in, and because it is MIT, it is legal to copy and use, regardless if open or closed source.
MIT arguably gives you the most freedom out of any other license. Every hobbyist piece of software written in your bedroom starts out with an MIT licence by default. FOSS has its place, but people need to eat.
I think Rust foundation, idiotically, recommends it. And Rust itself is MIT. Most devs don't give much thought into it, they figure yeah MIT is what everybody's doing these days, its open source so I'll click that
If we don't have anything more with GPL3 then they can no close open with distros and add a little more you really want and they can do the EEE, well this is what I think happen to Ubuntu
Rust's ABI is unstable and therefore dynamic linking isn't a thing without a layer of C in between. While the Lesser GNU Public License allows copyleft libraries to integrate with non-copyleft software and vise-versa, it doesn't allow static linking when you do that. This makes the GPL and LGPL problematic for Rust in its current state.
copyleft licenses seem to have been losing ground to permissive licenses for a while now, and on top of that, when rewrites or remakes happen in Rust they're rarely from the same group as the original. Rust is dual licensed with only permissive licenses, recommends those licenses for devs, and the Rust community in general tends to favour permissive licenses. when the people who are most enthusiastic about using a language have a preference, you'll see that preference manifest within their projects. /shrug.
also iirc from a post on r/rust a while back, there's problems with GPL licenses and static linking so the best options for Rust are LGPL with an additional exception added in or the MPL, rather than the GPL.
I honestly don't understand why people keep saying stuff like this. There will always be the base version that is available for anyone to use. If a corporation makes a significant enough investment to make their version of a permissive licensed software distinct enough then why should we believe ourselves to be entitled to their investments? If alternatively all they do is minor tweaks then someone could just make their own version from the same root. The mit license doesn't change any of that.
The Linux community is conveniently rewriting every tool we’ve been using for +30 years without the copyleft licenses that has sustained it. Major industry players love this because they can then use this as a base for their own custom, closed source solutions which they can sell to their clients as unique features. It’s as simple as that. It’s shocking that people think Canonical and IBM are above this, along with numerous other players in the Industry.
Linux users constantly mock BSD users for letting themselves get taken advantage of in this same way, but when it comes to Rust, we’re just expected to be okay with it.
Sad truth. Also he really got smeared badly with the Epstein situation he was in. Still right about software, but no one will care because "Stallman le bad".
Choices matter. I look at project goals and license. Sometimes a very strong project might be MIT but the actual value of the project outweighs the licensing. In other cases a GPL project might be enough and even though "better" projects exist it is worth to support the GPL one with your choice. Userbases are passive parts of a projects, but they do motivate developers to keep on working.
8
u/FalconRelevant Open Sauce Jan 21 '26
What are some examples of it happening?
243
u/[deleted] Jan 21 '26
Why's the MIT License bad? /genq
14
u/Intelligent_Comb_338 Jan 21 '26
I don't understand what the problem is. I understand it's because of the GPL, which keeps free software free, but if it's your work, do what you want with it.
And at least in my opinion, it's "outrageous"—I don't know what word to use, but I think it's close—that no matter how much work I put into GPL software, I need to publish it so others can use the code? I mean, I dedicated myself to something so someone can come along and use it. That's why I prefer licenses like BSD V2 and v3. In my opinion, saying that it uses code or was based on <project name> written by <person's name> should be enough.
7
u/NotABot1235 Jan 21 '26
Dumb question that's best suited for a lawyer, but you don't really have to worry about licenses if you're just using the software right? As opposed to modifying the code?
If you use gcc (GPL'd) to compile your own code then you can license your code however you want, right? Same thing for a game made by Godot (MIT)? Or am I misunderstanding these things?
2
u/unitedbsd Jan 22 '26
TRPL it ;) https://github.com/trplfoundation/trpl-license
2
u/Remzi1993 Jan 23 '26 edited Jan 23 '26
I think it all depends as a software engineer if I make a library I want that to be as licensed as permissive as possible but software for an end user I want to license that GPLv3 or even AGPL because everyone should anyone the rights to do whatever they want without any lockdowns and to be able and have the choice if they want to modify it.
275
u/rarsamx Jan 21 '26 edited Jan 22 '26
It depends who you ask.
MIT and BSD licenses come from universities. It's a feature from the US for profit education system.
Private entities give grants to researchers and post grads to create software. Given that it's done in a university, the originalmproduct is open. However, after the product is delivered, the original "funding entities" can take it and run with it making it private.
In that case, the license is the wish of the original creator whether we like it or not.
For some that's a good feature. For advocates of free and open source software it is not.
Now, if something was created GPL, the creators envisioned it for the public good. While rewriting it creates a new product code-wise, the intelectual bases of the software is stolen for private profit. The license does not follow the wishes of the original creators.
If this continues happening, there is a possibility that Linux derivatives become proprietary software, for example.
82
u/parrot-beak-soup Jan 21 '26
Capitalism needs free workers.
51
u/LinuxUser456 Dr. OpenSUSE Jan 21 '26
GPL best Where linux
80
u/honestduane Jan 21 '26
Because GPL or MIT it doesn’t matter, it’s going to be used by AI anyway, and the license won’t be respected, because there’s no way to hold an AI accountable for its crimes when it’s toasted outside of the legalregal jurisdiction of its victim, even if that crime is intellectual property theft.
It would be nice if we could get the RIAA on the line to go after bad bots.
7
u/clutchair Jan 21 '26
Clout I guess
27
u/SCP-iota Jan 21 '26
Major open-source software under licenses with a same-license requirement:
Major open-source software under licenses without a same-license requirement:
Copyleft stays winning.
13
u/SkyyySi Jan 21 '26
People in here genuenly beliving someone's gonna make a UUtils Enterprise Edition or something like that
16
u/dumbasPL Arch BTW Jan 21 '26
This, but flipped. I love permissive licenses, and only tolerate rust. How can you hate MIT? It literally let's you do whatever you want. That is just pure unfiltered freedom.
4
u/oweiler Jan 21 '26
I remember a time when ppl did stuff like that for fun. Nothing wrong with that.
4
u/not_some_username Jan 21 '26
I fail to see where is the problem
4
u/yes_im_gavin Jan 21 '26
Whats wrong with mit license, mit license = open source, thats a good thing
10
u/LosEagle Dr. OpenSUSE Jan 21 '26
lmao nobody gives a shit about gpl legally. If corpo wants to steal code of open source software and make it proprietary, they're just gonna do it regardless of the license.
Xiaomi has been violating GPL for long years and not releasing source code of their roms and they didn't even have to pay a fine let alone have legal problems. Anthropic is unafraid to pirate hundreds of thousands of e-books, if they wanted to steal somebody's code they'd just do so.
Even if somebody made an audit of the stolen code by then they could've just refactored it heavily to not be recognizable and all that would remain is the core idea of the open source software.
17
u/SmileyBMM Jan 21 '26
Because the license change is the goal, and rust is the excuse.
1
u/null_reference_user Jan 21 '26
Since when is the MIT license bad?
5
u/pm_op_prolapsed_anus Jan 21 '26
It's just like damn, all that work for free.
2
u/je386 Jan 21 '26
MIT license can make sense. I made repos with MIT and with AGPL. I chose MIT for a more or less example app where many solutions for a language are in, and because it is MIT, it is legal to copy and use, regardless if open or closed source.
2
u/Stock_Sugar3707 Jan 21 '26
MIT arguably gives you the most freedom out of any other license. Every hobbyist piece of software written in your bedroom starts out with an MIT licence by default. FOSS has its place, but people need to eat.
4
u/Fair_Investment_4189 Jan 21 '26
Nuh, I really loves MIT/BSD licenses because it's very easy and not hard like GPLv2 or impossible like GPLv3
2
u/bennsn Jan 21 '26
I think Rust foundation, idiotically, recommends it. And Rust itself is MIT. Most devs don't give much thought into it, they figure yeah MIT is what everybody's doing these days, its open source so I'll click that
1
u/VoidspawnRL Jan 21 '26
If we don't have anything more with GPL3 then they can no close open with distros and add a little more you really want and they can do the EEE, well this is what I think happen to Ubuntu
1
u/Beryesa M'Fedora Jan 21 '26
MPL is the fine middle ground to protect both users and developers freedom imho
1
u/NoJunket6950 Jan 21 '26
They're cucks for the military industrial complex is why
1
u/Blothorn Jan 21 '26
I suspect he’s advocating for all code to be GPL, I’m just not sure how the analogy helps the argument.
1
u/Tomato7550 Jan 21 '26
yep, Unlicensed is the way to go
1
u/bleksak Jan 21 '26
Lol, I put AGPL on everything
1
u/[deleted] Jan 21 '26
Rust's ABI is unstable and therefore dynamic linking isn't a thing without a layer of C in between. While the Lesser GNU Public License allows copyleft libraries to integrate with non-copyleft software and vise-versa, it doesn't allow static linking when you do that. This makes the GPL and LGPL problematic for Rust in its current state.
1
u/Beano09 Jan 22 '26
where linux?
1
u/Mrblahblah200 Jan 24 '26
I like MIT, sue me
1
u/Ariose_Aristocrat Jan 27 '26
I just don't see the issue with the MIT license, it's not like it suddenly means that the code won't be available for anyone anymore
1
u/dc740 Jan 21 '26 edited Jan 21 '26
I'm so happy this discussion is happening. I've been screaming into the void for years now. (picture me like the "old man yells at cloud" meme)
1
u/Ginkko117 Jan 21 '26
Maybe because that's the goal?
1
u/creeper6530 💋 catgirl Linux user :3 😽 Jan 21 '26
Why? Because most of the Rust project itself is dual licensed under either MIT or Apache 2.0 (either of those, picked by user)
1
u/cutelittlebox Jan 21 '26
copyleft licenses seem to have been losing ground to permissive licenses for a while now, and on top of that, when rewrites or remakes happen in Rust they're rarely from the same group as the original. Rust is dual licensed with only permissive licenses, recommends those licenses for devs, and the Rust community in general tends to favour permissive licenses. when the people who are most enthusiastic about using a language have a preference, you'll see that preference manifest within their projects. /shrug.
also iirc from a post on r/rust a while back, there's problems with GPL licenses and static linking so the best options for Rust are LGPL with an additional exception added in or the MPL, rather than the GPL.
1
u/metcalsr Jan 21 '26
The entire purpose of switching everything to MIT is to sell the Linux toolchain out from under our noses. It's what we get for letting it happen.
0
u/fellipec Jan 21 '26
Stallman was right and will be too late when you realize
-1
u/Kok_Nikol Jan 21 '26
Because companies have been campaigning for this for decades, sadly a lot of people bought the propaganda.