140

I would understand if Canonical want a new cow to milk, but why are developers even agreeing to this? Are they out of their minds?? Do they actually want companies to steal their code? Or is this some reverse-uno move I don't see yet? I cannot fathom any FOSS project not using the AGPL anymore. It's like they're painting their faces with "here, take my stuff and don't contribute anything back, that's totally fine"

top 50 comments
sorted by: hot top controversial new old
[-] brandon@lemmy.ml 110 points 3 months ago* (last edited 3 months ago)

The unfortunate reality is that a significant proportion of software engineers (and other IT folks) are either laissez-faire "libertarians" who are ideologically opposed to the restrictions in the GPL, or "apolitical" tech-bros who are mostly just interested in their six figure paychecks and fancy toys.

To these folks, the MIT/BSD licenses have fewer restrictions, and are therefore more free, and are therefore more better.

[-] bunitor@lemmy.eco.br 44 points 3 months ago* (last edited 3 months ago)

it's interesting how the move away from the gpl is never explicitly justified as a license issue: instead, people always have some plausible technical motivation. with clang/llvm it was the lower compile times and better error messages; with these coreutils it's "rust therefore safer". the license change was never even addressed

i believe they have to do this exactly bc permissive licenses appeal to libertarian/apolitical types who see themselves as purely rational and changing a piece of software bc of the license would sound too... ideological...

so the people in charge of these changes always have a plausible technical explanation at hand to mask away the political aspect of the change

[-] GnuLinuxDude@lemmy.ml 31 points 3 months ago

The rust coreutils project choosing the MIT license is just another gambit to allow something like android or chromeos happen to gnu+linux, where all of the userland gets replaced by proprietary junk.

And yet that's a popularly welcomed approach, for some reason. Just look at the number of thumbs down this has. https://github.com/uutils/coreutils/issues/1781

[-] bunitor@lemmy.eco.br 8 points 3 months ago

yeah, unfortunately most people in the foss community are the apolitical/free thinker types who hate the fsf bc it is "too political/evangelist" and don't want to understand how user freedom is affected by permissive licenses

load more comments (4 replies)
[-] 2xsaiko@discuss.tchncs.de 8 points 3 months ago* (last edited 3 months ago)

I use LLVM because it's good, but I would like it even more if it was GPL and I agree with OP's comment as well.

However, you're literally the guy that replies "oh, so you hate oranges" to people that say "I like apples" or however that meme goes. How about you don't completely twist people's justifications into something they never said.

edit: It comes down to that I have no say in whether other people want to allow their code to be exploited by corporations nor does it make a practical difference to me in what I can do with it, all I can do is say "you're an idiot" to them.

load more comments (1 replies)
[-] fossphi@lemm.ee 24 points 3 months ago

Add to this, the constant badmouthing of GNU and FSF from the crony bootlickers and sadly this is what we get

The tech crowd is also more of a consumer kind these days than the hacky kind, so it's much easier to push corporate shite with a little bit of polish on top

"apolitical" tech-bros who are mostly just interested in their six figure paychecks and fancy toys.

This, I understand.

laissez-faire "libertarians" who are ideologically opposed to the restrictions in the GPL

This, I do not. Apologies for my tone in the next paragraph but I'm really pissed off (not directed at you):

WHAT RESTRICTIONS???? IF YOU LOT HAD EVEN A SHRED OF SYMPATHY FOR THE COMMUNITY YOU WOULD HAVE BOYCOTTED THE MIT AND APACHE LICENSE BY NOW. THIS IS EQUIVALENT TO HANDING CORPORATIONS YOUR WORK AND BEGGING THEM TO SCREW OVER YOUR WORK AND THE FOSS COMMUNITY.

I feel a bit better but not by much. This makes me vomit.

[-] LeFantome@programming.dev 10 points 3 months ago* (last edited 3 months ago)

Since you seem so reasonable…

The restriction that some people object to is that the GPL restricts the freedom of the software developers (the people actually writing and contributing the code).

Most people would agree at first glance that developers should be able to license code that they write under whatever license they like. MIT is one option. Some prefer the GPL. Most see the right to choose a proprietary license for your own work as ok but some people describe this as unethical. I personally see all three as valid. I certainly think the GPL should be one of the options.

That said, if we are talking about code that already exists, the GPL restricts freedom without adding any that MIT does not also provide.

MIT licensed software is “free software” by definition. Once something has been MIT licensed, it is Open Source and cannot be taken away.

The MIT license provides all of the Free Software Foundations “4 freedoms”. It also provides freedoms that the GPL does not.

What the MIT license does not provide is guaranteed access to “future” code that has not yet been written. That is, in an MIT licensed code base, you can add new code that is not free. In a GPL code base, this is not possible.

So, the GPL removes rights from the developers in that it removes the right to license future code contributions as you want. Under the GPL, the right of users to get future code for free is greater than the right of the developer to license their future contributions. Some people do not see that as a freedom. Some even see it as quite the opposite (forced servitude). This “freedom” is not one of the “4 freedoms” touted by the FSF but it is the main feature of the GPL.

load more comments (2 replies)
load more comments (4 replies)
[-] azolus@slrpnk.net 22 points 3 months ago

Freedom for the rich and powerful to fuck over society and everyone else!

[-] avidamoeba@lemmy.ca 17 points 3 months ago* (last edited 3 months ago)

Yeah, that's all there's to it, along with pure ignorance. In a past not so ideologically developed life, I've written code under Apache 2 because it was "more free." Understanding licenses, their implications, the ideologies behind them and their socioeconomic effects isn't trivial. People certainly aren't born educated in those, and often they reach for the code editor before that.

[-] bunitor@lemmy.eco.br 34 points 3 months ago* (last edited 3 months ago)

it's been a trend for a while unfortunately. getting rid of the gpl is the motivation behind e.g. companies sponsoring clang/llvm so hard right now. there are also the developers that think permissive licenses are "freer" bc freedom is doing whatever you want /s. they're ideologically motivated to ditch the gpl so they'll support the change even if there's no benefit for them, financial or otherwise.

[-] A_norny_mousse@feddit.org 19 points 3 months ago

getting rid of the gpl is the motivation behind e.g. companies sponsoring clang/llvm so hard right now

And there it is. Follow the money.

They are maliciously harming the community. They need to be named and shamed. I still seethe at OpenBSD using it. Why is it so hard for them to understand? Why do they want to give away their work for the taking to corporations who just want to make money off of their backs?

load more comments (4 replies)
[-] LeFantome@programming.dev 9 points 3 months ago

Some people might say that so many companies contributing free and open code to clang/llvm instead of GCC is real world evidence against the idea that companies only contribute to free software because the GPL makes them. Or even that permissive licenses can lead to greater corporate sharing than the GPL does. Why does Apple openly contribute to LLVM but refuse to ship GPL3 anything?

According to the web, Red Hat is the most evil company in Open Source. They are also the biggest contributor to Xorg and Wayland. Those are MIT licensed. Why don’t they just keep all their code to themselves? The license would allow it after all. Why did they license systemd as GPL? They did not have to.

The memory allocator used in my distro was written by Microsoft. I have not paid them a dime and I enjoy “the 4 freedoms” with the code they gave me because it is completely free software. Guess what license it uses?

load more comments (1 replies)
load more comments (2 replies)
[-] danielquinn@lemmy.ca 17 points 3 months ago

Here's a fun idea, let's fork these MIT-based projects and licence them under the AGPL :-)

[-] LeFantome@programming.dev 10 points 3 months ago

You could do that. MIT is a very free license.

Of course, that would only be a useful thing to do if you were also going to contribute to the code.

load more comments (5 replies)
load more comments (1 replies)
[-] savvywolf@pawb.social 16 points 3 months ago

here, take my stuff and don’t contribute anything back, that’s totally fine

I mean, yeah? They are probably fine with that and think that software should be distributed without restrictions. You may not agree with it, but it's their choice. Not really stealing if they give it away willingly.

I cannot fathom any FOSS project not using the AGPL anymore.

I mean, most of them that want to use a GPL-like license use the GPL or LGPL rather than the AGPL. :P

why are developers even agreeing to this?

Are they? Last I checked this wasn't as much of a plan as much of it was just a developer thinking out loud. And even if it was a real plan, developers should continue doing what they should be doing anyway: Write their scripts without any GNU/uutils/whatever-microsoft-calls-their-evil-uutils-fork extensions. Then their scripts could run across all platforms, including GNU, uutils, FreeBSD and BusyBox.

At any rate, if Microsoft really wanted to make their own coreutils fork (if they haven't already), they're not really that complicated tools. They could devote like maybe a year of engineering time and get it pretty much compatible.

load more comments (4 replies)
[-] LeFantome@programming.dev 16 points 3 months ago* (last edited 3 months ago)

Apple makes the source code to all their core utilities available? Nobody cares but they do.

Why do they?

They are BSD licensed (very similar to MIT). According to the crowd here, Apple would never Open Source their changes. Yet, in the real world, they do.

Every Linux distro uses CUPS for printing. Apple wrote that and gave it away as free software.

How do we explain that?

There are many companies that use BSD as a base. None of them have take the BSD utils “commercial”.

Why not?

Most of the forks have been other BSD distros. Or Chimera Linux.

How about OpenSSH?

It is MiT licensed. Shouldn’t somebody have embraced, extended, and extinguished it by now?

Why haven’t they?

[-] cypherpunks@lemmy.ml 32 points 3 months ago

Apple makes the source code to all their core utilities available

Apple makes the source code for many open source things they distribute available, but often only long after they have shipped binaries. And many parts of their OS which they developed in-house which could also be called "core utilities" are not open source at all.

Every Linux distro uses CUPS for printing. Apple wrote that and gave it away as free software.

Apple did not write cups.It was was created by Michael R. Sweet in 1997, and was GPL-licensed and used on Linux distros before Mac OS X existed. Apple didn't want to be bound by the GPL so they purchased a different license for it in 2002.

Later, in 2007 they bought the source code and hired msweet to continue its development, and at some point the license of the FOSS version was changed to "GNU General Public License ("GPL") and GNU Library General Public License ("LGPL"), Version 2, with an exception for Apple operating systems."

In 2017 it was relicensed Apache 2.0.

Finally, "In December 2019, Michael left Apple to start Lakeside Robotics. In September 2020 he teamed up with the OpenPrinting developers to fork Apple CUPS to continue its development. Today Apple CUPS is the version of CUPS that is provided with macOS® and iOS® while OpenPrinting CUPS is the version of CUPS being further developed by OpenPrinting for all operating systems."

[-] unalkalkan@lemmy.world 10 points 3 months ago

I loved this comment as much as a person is allowed to love it

load more comments (1 replies)
[-] ipkpjersi@lemmy.ml 15 points 3 months ago* (last edited 3 months ago)

For me, my personal projects are generally MIT licensed. I generally don't like "restrictions" on licenses, even if those "restrictions" are requiring others to provide their source and I want as many people to use my projects as possible, I don't like to restrict who uses it, even if it's just small/home businesses who don't want to publish the updated source code. Although, I admit, I'm not a huge fan of large corporations potentially using my code to generate a profit and do evil things with it, but I also think that's not going to be very common versus the amount of use others could get from it by having it using MIT who might not be able to use it otherwise with AGPL.

With that said, though, I have been starting to come around more to AGPL these days.

[-] ReakDuck@lemmy.ml 13 points 3 months ago

I wohld agree, because you really downplay the scenario.

As soon as you accidentallt create something, which everyone starts to use or has an use case, then some Cooperation will copy that thing, make it better and make your community dissappear because there is the newer tool which you cant change the code of anymore and need to use a monthly subscription or something to even use.

So, it somehow seems like you're gaslighting yourself by downplaying the use case.

Mostly it will be small buisnesses and hobbyists, which I would like to code for them too. Especially when they are nice and friendly. But as soon as Microsoft, Google, Meta, Amazon gets hands on it and sees a potential to squeeze money through it by destroying it, then they will surely do it.

load more comments (5 replies)
[-] KingThrillgore@lemmy.ml 15 points 3 months ago* (last edited 3 months ago)

Its simple: its to exploit it in a corporate setting. I license under MIT because a lot of my things are of small convenience, but never without debating the ethics of why I am licensing it.

GNU is the enemy to capitalism and if you need more proof, look at what Apple has done with LLVM/Clang and CUPS. We need GNU more than ever.

I understand that if your boss tells you to write MIT/Proprietary code, you do so. I just wish that the ones who had a choice would use GPL

load more comments (1 replies)
[-] cypherpunks@lemmy.ml 12 points 3 months ago

fyi: GNU coreutils are licensed GPL, not AGPL.

there is so much other confusion in this thread, i can't even 🤦

[-] phlegmy@sh.itjust.works 12 points 3 months ago

If you're developing software for a platform that doesn't allow users to replace dynamic libraries (game consoles, iOS, many embedded/commercial systems), you won't be able to legally use any GPL or AGPL libraries.

While I strongly agree with the motives behind copyleft licenses, I personally never use them because I've had many occasions where I was unable to use any available library for a specific task because they all had incompatible licenses.

I release code for the sole purpose of allowing others to use it. I don't want to impose any restrictions on my fellow developers, because I understand the struggle it can bring.

Even for desktop programs, I prefer MIT or BSD because it allows others to take snippets of code without needing to re-license anything.

Yes I understand that means anyone can make a closed-source fork, but that doesn't bother me.
If I wanted to sell it I might care, but I would have used a different license for a commercial project anyway.

load more comments (7 replies)
[-] TMP_NKcYUEoM7kXg4qYe@lemmy.world 9 points 3 months ago
load more comments (5 replies)
[-] Bogus5553@lemm.ee 8 points 3 months ago

MIT/GPL is fine for smaller tools.

[-] GnuLinuxDude@lemmy.ml 7 points 3 months ago

For small programs the FSF/GNU even suggests considering not using the GPL https://www.gnu.org/licenses/license-recommendations.html

load more comments (1 replies)
[-] kogasa@programming.dev 6 points 3 months ago* (last edited 3 months ago)

Yeah, specifically for something like coreutils I can't see the malicious endgame that is suggested by others here. Is the fear that a proprietary version of cat or pwd or printf takes over the ecosystem and then traps users into a nonfree agreement? Or a proprietary coreutils superset that offers some new tool and does the same thing? Or a proprietary coreutils that generates profit for businesses without attribution to the developers? What would stop anyone from just writing their own proprietary set of tools to do the same thing now, even if uutils didn't exist? Clearly not much, since uutils did exactly that (minus the proprietary bit).

I personally don't see a compelling reason to change to MIT, but I also don't see the problem.

[-] crystalwalrus@programming.dev 6 points 3 months ago

What's stopping people from doing that today is network effects. There are enough differences today between bsd coreutils and gnu coreutils that substituting one for the other doesn't work out of the box.

The chain of events that would cause a problem are: due to Ubuntu popularity rust MIT core utils overtakes gnu coreutils and people drop support for gnu coreutils, then a large and we'll funded corporate entity could privately fork rust coreutils and lock people in.

load more comments (2 replies)
[-] OprahsedCreature@lemmy.ml 8 points 3 months ago

Honestly it's probably just because so many devs are involved more in their code and don't want to worry about the nuances and headaches involved in licensing. MIT is still open source.

I guess I can't really fault that. Developers not interested in the license they use to publish code baffles me

[-] limer@lemmy.dbzer0.com 6 points 3 months ago

Speaking for myself, it’s because future monetization can be easier under mit when using a foss utility and private code.

My project would not exist at all unless there were ways to make money off it.

True, others can also use that same code too, in the exact same way, but that requires quite the investment, and those of us that are doing this are banking on not getting the interest of a monopoly in that way. We are competing against other small businesses who have limited resources.

At the same time the free part can get a boost by the community.

I comment a lot in politics here, and am sometimes an ass, so cannot name this project

[-] bunitor@lemmy.eco.br 6 points 3 months ago

not sure how it would be more difficult to make money using gpl tools

load more comments (4 replies)
[-] why@lemmy.sdf.org 6 points 3 months ago

I worked on an oss library with an MIT license and my colleagues told me they with that instead of GPL was with GPL it basically forces anyone who uses the library to make everything in their project available.

[-] marauding_gibberish142@lemmy.dbzer0.com 11 points 3 months ago* (last edited 3 months ago)

Only if they make changes/improvements to the code. If it's a library that is used then no, AFAIK you don't need to. If everyone using GPL code had to make their entire project FOSS then TPLink and DLink wouldn't have any market share. The only reason OpenWRT exists is because Linksys was forced to open up their code because they had illegally refrained from opensourcing their code, which was a great positive for the community

load more comments (5 replies)
load more comments
view more: next ›
this post was submitted on 24 Mar 2025
140 points (100.0% liked)

Linux

55692 readers
566 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago
MODERATORS