
Lol, very first pair of comments. I love phoronix sometimes.

Lol, very first pair of comments. I love phoronix sometimes.
Replace a perfectly usable GPL software for MIT? Nope. I used to fall for that ten years ago. The social infrastructure of software is more important than the exact tech used. The license is fundamental to that.
What did you replace Xorg with 10 years ago?
Nothing. Still use it to present day. I generally trust the selection of OS software to the distro developers - Debian and Ubuntu for me. We constantly use software that doesn't perfecty fit our requirements or wants.
Not the person you asked but kwin the GPL licensed Wayland compositor. Why do you ask?
We like the Rust, we hate the cuck license. Simple.
I don't understand what's going on with the rust community insisting on cuck licences. Do they love writing on their Mac books so much?
I think a part of it may be that they are from the younger generation like myself, and most of them don't really know the history of software and FOSS, and MIT is just a safe option for them. I think they haven't really put in the time to read and undertstand the philosophy and logic behind FOSS and read the licenses and writings.
But why MIT? How come that became the default? Why not GPL? Is Microslop Github suggesting MIT by default?
I'm not sure but theres something in my mind bout MIT being the first suggested license for github.
and also, to be real, you need to do some reasearch and actually understand the GPL license if you want to use it for your project. But with MIT you can just slap it on there and forget. It's convenient, but like a lot of conveniences, can be very bad.
Why do you need to do research for GPL? It's the OG opensource license AFAIK that forces users to also opensource their stuff. MIT let's anybody close source your code and make money with it.
GPL isn't perfect as it doesn't solve the funding problem, but MIT is about the worst thing one can do for opensource: do the work for companies, for free, and be OK with never contributing back to the opensource ecosystem.
The OG open-source license was when software was just shared as a convenience, as companies only sold the matching hardware. When AT&T started asking for license fees for UNIX, it all went downhill.
The compatibility stuff really do need understanding.
You can't use all other projects in your GPL project and your GPL project cant be used within every project.
permissive licenses really do have no compatibility since they forbid nothing and allow everything (which isnt good most of the time) so tgey are simpler to use.
Now that you mention it, it is kinda strange. MIT has been abused before.
You're a rube if you think corporations can't throw some money at interns do a rewrite in MIT and bypass GPL that way.
So let them do that. Why should we be doing their dirty work for them?
Unless we're stupid.
Hmm sorry for calling you a Rube. You make a fair point.
@Maddier1993 @duelistsage Average Twitter post
So are you saying that the developers should abandon the project if they do not use a license that you like?
It's not about any of us enjoying the license*, it's about preserving the integrity of free software. It's both flattering and disturbing that core utils is popular enough that people have decided to give them away to anyone who would want to take them without ever contributing back. If those people are found out there will be no legal recourse. Those Rust rewrites would inevitably be made proprietary without any credit for the authors.
First GNU coreutils is going to remain GPL-licensed, so nothing that already exists is being given away; the only thing that is happening is that some people have decided to write brand new code. (And it is worth noting that GPL only says that if you share the binaries, you have to share the source code; if your changes are only used internally, you do not have to contribute them back, though you probably want to do so since it makes your life easier down the road when you want to use newer version of upstream.)
Second, what scenario exactly is it that you are worried about? I want a specific and plausible answer, not just vague allusions.
Finally, if the Rust authors are fine with the possibility that someone will use their code in this way, then who are we to tell them to stop their development when we can continue to use GNU coreutils?
You did not answer my question, and I think it is an important one so I will repeat it: should they abandon the project if they are unwilling to use your preferred license?
I wrote this before I realized that you don't actually care about the answer, you just want people to shut up about it, so sorry. If you want somebody to do the work you'll have to do it yourself now. You've been given plenty of examples in this thread already
I have not been given a specific example of a scenario involving uutils, I have only been told about scenarios for unrelated and very different projects, and the difference between the situations is significant enough that you can't simply point to them and declare that your point has automatically been proven. In fact, I would argue that uutils is such a different case that it is implausible that such a scenario could occur and become a big problem.
And yes, people stopping complaining about work being done on a project they are not involved with in every single post discussing it would be a perfectly fine outcome for me. But if they are not going to do that, then I would also be happy with getting my questions answered because I believe that they are relevant.
I think the biggest point you may be missing here is if you start re-writing GNU/Linux (which is what uutils is the first step in doing) with an MIT license, you start making reasons for commercial entities that contribute back out of obligation to stop supporting upstream free software. This is a no brainer to me. As to whether or not anybody should stop writing uutils, the answer is **obviously not. ** The license, however, is free game for scrutiny
Okay, but is this group trying to re-write all of the GPL software in the Linux ecosystem with an MIT license? I ask this because I think that the words "first step" are doing a lot of the lifting in your argument.
And just to be clear, my objection is not to people disagreeing with the license; in fact, as I have said elsewhere--though I hardly expect you to have read all of my comments here!--I think that the underlying criticism is actually reasonable, I just also think that the extent of the concern is exaggerated in practice in this specific case (which is why I keep trying to pin people down on specifics rather than generalities). Again, my objection is that people feel the need to post the same inane comments with varying degree of toxicity (such referring to them as using a "cuck" license) complaining about it in every single post.
Yeah I don't toxicity either it helps nobody. But if you would allow me to be a little vulgar, here's a quick attempt to aggregate why the legal side of GPL has been important:
https://claude.ai/share/ad5124a7-ddad-4ec8-8b4f-d270242dcf56
Search engines take a bunch of time and I gotta keep parenting.
Also* it took decades for GNU/Linux to accrue enough momentum to get to a point where it is today: a commercially viable cloud powerhouse. It didn't get here by letting anybody/everybody just do what they want with the software. These small flights accumulate to protect an entire ecosystem of beloved software, which is why many of us feel the need to use the only voice we have. I don't think for sure that anybody wants to replace Linux with a permission version but the benefits for greedy corporations to see that happen is pretty clear. Especially when people are willing to start doing that for free
Your ignorance is annoying.
They never should've gone with a weak license to begin with.
Whoever is suggesting and perpetuating MIT over GPL needs to be tarred and feathered.
it still has a permissive license :(
You are very right. While non-copyleft licences makes sense for some software (a game engine like Godot, for example, released under the MIT licence) it's absolutely awful for the coreutils.
I wasn't aware that the coreutils software was changing its license?
As far as I know uutils has always been under an mit licence, hasn't it?
What's wrong with a permissive licence?
GPL or GTFO! On a more serious note: Permissive licenses open a project up to unilateral exploitation by commercial entities and can lead to fractured ecosystems.
On a more principled note: permissive licenses (as compared to free software licenses) undermine the free software ecosystem and the freedoms it brings in the long term and the thing that uutils is doing - that is taking a GPL licensed project and rewriting it under a more permissive license is corrosive to free software. GPL applies not when corporations use a piece of software, but when they distribute binaries back to you. This is not about limiting the rights of corporations but about protecting the digital freedom of people.
It allows corporations to take without giving back.
It's why Sony and Apple based their operating systems on BSD over Linux.
It allows uuitls, which is an important piece of closed source software, to be used in properitary software. and that is bad.
Isn't it open source? Why is it being in proprietary software bad?
The theoretical concern is that some nefarious company will start making improvements and not contribute them back so that it can have access to (and possibly even sell) its own premium version that takes advantage of the hard work of the community without giving back.
Personally, I am a bit skeptical of this for a couple of reasons. First, I have a really hard time seeing any company care enough about uutils to do this. Second, continually merging changes from an upstream project is a real pain, so there is a strong incentive to make contributions back out of self-interest.
But even to the extent that there is some grounds to be concerned, it is not enough for so many people to contribute so much noise to every single one of these posts whining, as if it is attack on them personally.
This. Licenses are so that trust is not needed and being a good FOSS citizen is expected. That means publishing your code if you fork, giving proper attibution and granting your users the same rights as the original project did.
Something very normal.
Okay, but if the developers of uutils do not care about these things, and they would be the ones most hurt because they would not get access to the changes that others are making... why should the rest of us make a big deal over it?
Because we are users, contributors, packagers, distributors... and if the project is unsustainable and suddenly becomes proprietary that is bad.
Or if the project is included in proprietary systems. Nobody will have the right to get source code then, or in case of GPLv3 even the right to install other software.
Copyleft and GPLv3 grant users the rights to prevent e-waste or replace shitty proprietary software on useful hardware with better one.
Copyleft licenses spread these rights, while permissive ones do nothing apart from handing out software for nothing in return.
So, in your opinion, should these developers simply stop their work on this project of they are not willing to use the GPL?
No, but as they do great work it is a shame that they dont protect it and thereby reduce the protection of every distro shipping them
Fair enough. I do actually get the concern, though I think that the threat is being exaggerated. However, I would argue that, if the goal is not to try and get these developers to abandon their efforts, then it does not make sense for every single discussion to get flooded with the same complaints about the license to the point that not much else seems to get talked about.
Because it is not my decision as it is not my project, and I do not like to constantly be making big deal about other people's decisions unless there is a significant chance of them having a significantly negative impact on my life, which I do not see in this case.
What freedom is being taken away from you, personally, exactly, that makes it so bad that they decided to go with this license?
Not the commenter you're asking, but I do consider the MIT licence a bad one for something like a core part of an OS. Not all FOSS licences are created equal, there're even important differences between the different GPLs (GPL2 is more permissive than GPL3, for example. With AGPL you have to grant the freedoms to the users even if the software is running out of your server, which isn't a thing with GPL2/3), and even the most permissive ones have a reason to exist, but I'm yet to hear (or read) a good one for these uutils, so I'm not touching any distro or project that uses these mit core utils with a ten foot pole.
It's not a matter of "him" personally. Permissive license allow for a work to be taken and redistributed by other entities, without enforcing them to release their changes. This creates a one way relationship that is generally detrimental to the open source ecosystem, allowing work to be stolen away from the public. That being said, choosing a license is situational, and a permissive one can be a great choice in certain instances. For that particular case, I don't see much benefit to having a permissive licence.
Okay, so it sounds like in practice this would primarily affect the uutils developers by denying them access to these changes. However, they are the ones who deliberately chose this license, so why make a big deal of it in every single uutils thread?
Are you going to complain about this every time uutils is posted?
Yes.
Because I can.
And also, as the other two commenters said, it's a valid complaint for something as important as coreutils.
Just because you can add noise to a discussion does not mean that you have to.
Licencing is a legitimate concern (not noise), even more so considering it's for the core utils
So it needs to be commented on in every single article?
If so, is that going to change anything?
So it needs to be commented on in every single article?
Yes
If so, is that going to change anything?
Potentially.
The alternative is not bringing up the concern and it goes forgotten until it is too late and we are stuck with the results of bad decisions for no good reason.
Developers voicing their concerns is the only way things can change for the better.
Here's two examples:
Redis licensing rug pull
Google's JpegXL whiplash
And there's plenty of other examples (e.g. Microsoft against linux -> WSL support, etc...)
If developers don't voice their concerns, then things stop changing for the better.
Whose opinion do you actually think is going to be changed? All I see here is a lot of preaching to the choir here. If I were a uutils developer, I would stay far away from all of these discussions because of how much hate is directed towards it.
If they do not adopt the license you prefer, would it be better for them to just go ahead and abandon the whole effort? Are there efforts really so valueless simply because they chose the license that they did? Moreover, is dictating to volunteers what license they should be using for their code what you think this community should be about?
You claim that it is important that people make tons noise in every single post on uutils because it will prevent a bad scenario down the line, but could you detail what that scenario is? Because people like to make allusions to such a scenario constantly but refuse to get specific and then engage on a discussion on the specifics.
Incidentally, your choice of Redis is an example exactly illustrates my point that this license is not a gigantic deal it shows that the worst case scenario is... uutils being forked. Heck, it can even be forked at any time with a copyleft license precisely because its existing language is permissive.
If I were a uutils developer, I would stay far away from all of these discussions because of how much hate is directed towards it.
I only see the hate towards this project being either from anti-rust trolls, or misdirected hate from Ubuntu towards switching to a new coreutils implementation on an LTS release before full compatibility has been achieved. I don't see any hate in regards to licensing.
If they do not adopt the license you prefer, would it be better for them to just go ahead and abandon the whole effort? Are there efforts really so valueless simply because they chose the license that they did?
Their efforts have value, but the value is limited by its current license. MIT licenced projects have a recurring history of being improved privately without those improvements going back into the project. It leads to a lot of duplicated, wasted effort. There may also be the potential for patent issues with the licence. No one wants to deal with some litigious asshole or company going after the project turning it radioactive.
Moreover, is dictating to volunteers what license they should be using for their code what you think this community should be about?
I think bringing up issues with the project is definitely something that should be brought up. As for dictating which particular licence is used, that's up to the contributors, but that doesn't mean others can't give their input. It's also likely that most of the contributors will want a license that allows the project to safely continue into the future.
You claim that it is important that people make tons noise in every single post on uutils because it will prevent a bad scenario down the line, but could you detail what that scenario is? Because people like to make allusions to such a scenario constantly but refuse to get specific and then engage on a discussion on the specifics.
I thought the Redis example was a good example of this.
I continue on this point further down, but I'm leaving this right now to stay on topic with redis.
Incidentally, your choice of Redis is an example exactly illustrates my point that this license is not a gigantic deal it shows that the worst case scenario is… uutils being forked.
The community was fractured. A report by an enterprise support company said 75% of existing redis users were motivated to seek alternatives. I'm not sure what number you would consider to be a gigantic deal, but Redis certainly thought it was, otherwise they would not have reverted back to the previous license.
Heck, it can even be forked at any time with a copyleft license precisely because its existing language is permissive.
It can be forked, but relicensing can mean needing permission from every contributor of the original, and/or removing all contributions from those who don't agree to the new licence. Not to mention the community fracturing, and legal issues. It's a massive effort that can be prevented by the original project choosing a better license earlier.
You claim that it is important that people make tons noise in every single post on uutils because it will prevent a bad scenario down the line, but could you detail what that scenario is? Because people like to make allusions to such a scenario constantly but refuse to get specific and then engage on a discussion on the specifics.
Well this comment is probably getting too long, so I'll simply point you towards the busybox licensing drama.
I agree that being concerned is reasonable. The reason for my fervor is that I find it unreasonable for every single discussion of uutils to be flooded with complaints about the license--that are often very toxic, e.g. reference to uutils using a "cuck license" as one commenter did above--to the point that there are few discussions of anything else.
Then make a top level comment that kicks off the type of discussion you want.
For all your comments, not a single one was a reply to the post itself. Lots of comments presenting your POV (totally fair), others that call the contributions of others noise because you think their POV is low value and over represented.
Your posting style may come from a good place, but it’s very adjacent to sealioning. Be the change that you want to see, not a comment warrior creating engagement in every comment thread where someone on the internet is wrong.
It is not just that these complaints are noise, but that they contribute to a general environment of toxicity by complaining about other people working on a project they are passionate about, which is something I abhor. To the extent that I am coming across as being toxic myself (which is not an unreasonable viewpoint in many, but not all, cases), I consider that to be me holding up a mirror of the comment I am responding to.
You did not address the core issue, which is that you engage with many comment threads negatively and on an individual basis, providing a cyclical viewpoint. This is creating engagement for each “toxic” thread individually instead of confidently asserting a PoV and letting it rest. I understand that from your perspective that it’s fair to lower yourself to their perceived level, but it’s still bloating the toxic side of the discourse instead of helping it move on.
Drop a wall of well reasoned text and let it stand on its own. Or provide the type of comment that you want to see at the top level and be the change you want.
Case in point, I’ve said what I wanted to say, have found myself restating it once, and this comment is my peace out. A good day to you!
It does not mean i can't.
And that's all i care.
It is trolling when it broke production level systems?
To be fair im NOT blaming the rust util team. I hope the best for them. But it was a bad decision to use something like that to power systems before it was fully tested and ready. It broke many different things in prod at work and we had to switch over to another distro entirely. Which was a lot of work. It made us stop using Ubuntu which is a shame.
Your first mistake was using Ubuntu on a production server. Canonical has made more than enough questionable decisions over the past decade that using Ubuntu for a production system should be a red flag.
Your probably right. It was an old setup but ill own it. I inherited it (mitus touch) so I probably should have put more effort into switching.
Switching can be hard sonetimes. At work we still have a few Ubuntu 20.04 LTS machines that need to be replaced.
It is trolling when it broke production level systems?
Depends. Were they the ones who put it into production level systems? If the answer to that question is no, then, well, you have your answer already.
https://ubuntuhandbook.org/index.php/2025/10/ubuntu-announced-fix-2510-updates/
This specifically broke things at work and is why we moved off.
i mean, how many realistically? how many systems are out there using non-LTS releases that would actually run into these edge cases? and auto-updating them in production without triggering the bug first? or maybe i’m a naive corpo
Honestly it was a bunch of docker containers that failed all around the same time. Kinda sucks. Again I blame more Ubuntu support (since we pay for it) than rust or rust utils.I hope to eventually switch all systems to using the library when they hit 100%. Its going to be so fast :)
What broke? If it was a GNU ism that wouldn't work on *BSD either, than it is your own stupid fault. There are other linux distros that also don't use the gnu core utils that would break things do.
top 94 comments