this post was submitted on 16 Jun 2024
7 points (100.0% liked)

linuxmemes

28647 readers
1032 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
     

    Context:

    Permissive licenses (commonly referred to as "cuck licenses") like the MIT license allow others to modify your software and release it under an unfree license. Copyleft licenses (like the Gnu General Public License) mandate that all derivative works remain free.

    Andrew Tanenbaum developed MINIX, a modular operating system kernel. Intel went ahead and used it to build Management Engine, arguably one of the most widespread and invasive pieces of malware in the world, without even as much as telling him. There's nothing Tanenbaum could do, since the MIT license allows this.

    Erik Andersen is one of the developers of Busybox, a minimal implementation of that's suited for embedded systems. Many companies tried to steal his code and distribute it with their unfree products, but since it's protected under the GPL, Busybox developers were able to sue them and gain some money in the process.

    Interestingly enough, Tanenbaum doesn't seem to mind what intel did. But there are some examples out there of people regretting releasing their work under a permissive license.

    all 21 comments
    sorted by: hot top controversial new old
    [–] TheImpressiveX@lemmy.ml 4 points 2 years ago (2 children)

    The MIT license guarantees freedom for developers. The GPL guarantees freedom for end users.

    [–] TheOubliette@lemmy.ml 4 points 2 years ago (1 children)

    The MIT license guarantees that businesses will use it because it's free and they don't have to think about releasing code or hiding their copyright infringement. The developers I've seen using that license, or at least those who put some thought into it, did do because they want companies to use it and therefore boost their credibility through use and bug reports, etc. They knowingly did free work for a bunch of companies as a way to build their CV, basically. Like your very own self-imposed unpaid internship.

    The GPL license is also good for developers, as they know they can work on a substantial project and have some protections against others creating closed derived works off of it. It's just a bit more difficult to get enterprise buy-in, which is not a bad thing for many projects.

    [–] CapeWearingAeroplane@sopuli.xyz 0 points 2 years ago* (last edited 2 years ago) (1 children)

    You're not seeing the whole picture: I'm paid by the government to do research, and in doing that research my group develops several libraries that can benefit not only other research groups, but also industry. We license these libraries under MIT, because otherwise industry would be far more hesitant to integrate our libraries with their proprietary production code.

    I'm also an idealist of sorts. The way I see it, I'm developing publicly funded code that can be used by anyone, no strings attached, to boost productivity and make the world a better place. The fact that this gives us publicity and incentivises the industry to collaborate with us is just a plus. Calling it a self-imposed unpaid internship, when I'm literally hired full time to develop this and just happen to have the freedom to be able to give it out for free, is missing the mark.

    Also, we develop these libraries primarily for our own in-house use, and see the adoption of the libraries by others as a great way to uncover flaws and improve robustness. Others creating closed-source derivatives does not harm us or anyone else in any way as far as I can see.

    [–] TheOubliette@lemmy.ml 0 points 2 years ago

    If the government is the US (federal), I think you are technically supposed to release your code in the public domain by default. Some people work around this but it's the default.

    But anyways, the example you've given is basically that you're paid with government funds to do work to assist industry. This is fairly similar to the people that do the work for free for industry, only this time it's basically taxpayersl money subsidizing industry. I've seen this many times. There is a whole science/engineering/standards + contractor complex that is basically one big grift, though the individual people writing the code are usually just doing their best.

    I'm also an idealist of sorts. The way I see it, I'm developing publicly funded code that can be used by anyone, no strings attached, to boost productivity and make the world a better place. The fact that this gives us publicity and incentivises the industry to collaborate with us is just a plus.

    Perhaps it makes the world a better place, perhaps it doesn't. This part of the industry focuses a lot on identifying a "social good" that they are improving, but the actual impact can be quite different. One person's climate project is another's strategic military site selector. One person's great new standard for transportation is another's path to monopoly power and the draining of public funds that could have gone to infrastructure. This is the typical way it works. I'm sure there can be exceptions, though.

    Anyways, I would recommend taking a skeptical eye to any position that sells you on its positive social impact. That is often a red flag for some kind of NGO industrial complex gig.

    Calling it a self-imposed unpaid internship, when I'm literally hired full time to develop this and just happen to have the freedom to be able to give it out for free, is missing the mark.

    Well you're paid so of course it wouldn't be that.

    Also, we develop these libraries primarily for our own in-house use, and see the adoption of the libraries by others as a great way to uncover flaws and improve robustness. Others creating closed-source derivatives does not harm us or anyone else in any way as far as I can see.

    Sometimes the industries will open bug reports for their free lunches, yes. A common story in community projects is that they realize they're doing a lot of support work for companies that aren't paying them. When they start to get burned out, they put out calls for funding so they can dedicate more time to the project. Sometimes this kind of works but usually the story goes the other way. They don't get enough money and continue to burn out. You are paid so it's a bit different, but it's not those companies paying you, eh?

    You aren't harmed by closed source derivatives because that seems to be the point of your work. Providing government subsidy to private companies that enclose the derivative product and make money for their executives and shareholders off of it.

    [–] Andromxda@lemmy.dbzer0.com 1 points 2 years ago

    The MIT license guarantees freedom for ~~developers~~ proprietary software conglomerates to use FOSS code in their proprietary products. The GPL guarantees freedom for ~~end users~~ the entire FOSS community, both for users and developers.

    [–] db2@lemmy.world 2 points 2 years ago (2 children)

    Permissive licenses (commonly referred to as "cuck licenses")

    That's where I stopped reading. πŸ‘Ž

    [–] homesweethomeMrL@lemmy.world 1 points 2 years ago (1 children)

    I mean, it’s funny for a couple of reasons

    [–] criss_cross@lemmy.world 1 points 2 years ago (1 children)

    Yeah I don't think I've ever heard that term before in my life and I've been doing this for a while.

    And I don't think I ever wanna hear it again.

    [–] db2@lemmy.world -1 points 2 years ago

    It's a term Trump cultists use.

    [–] nUbee@lemmy.world 2 points 2 years ago

    When I think of Copyleft licenses, I just think of it as "Use this program as you see fit, but if you share/redistribute it, you may not add any restrictions to it."

    I don't understand why there are communities that hate GPL so much. It is such a powerful license that practically guarantees that the program will be free for any who wants it, it just won't allow someone to add restrictions to it.

    I've heard arguments against the GPL like: "It's too restrictive!" Only if you want your program to be muddled with any kind of program that doesn't respect freedom. Saying the GPL is too restrictive to developers is like saying the 13th amendment of the US Constitution is too restrictive to slave owners.

    [–] nomadjoanne@lemmy.world 1 points 2 years ago

    Tannenbaum is fucking asshole. Isn't he the idiot that told Torvalds "you certainly would have failed my class if you submitted your OS as a final project?"

    The guy deserves no respect.

    [–] pmk@lemmy.sdf.org 1 points 2 years ago* (last edited 2 years ago) (3 children)

    People seem to think that those who choose permissive licences don't know what they're doing. Software can be a gift to the world with no strings attached. A company "taking" your code is never taking it away from you, you still have all the code you wrote. Some people want this. MIT is not an incomplete GPL, it has its own reasons.

    For example, OpenBSD has as a project goal: "We want to make available source code that anyone can use for ANY PURPOSE, with no restrictions. We strive to make our software robust and secure, and encourage companies to use whichever pieces they want to."

    [–] Terevos@lemm.ee 1 points 2 years ago

    I don't get the whole MIT vs GPL rivalry. They both have their uses. If you want to use GPL, go for it. And if you want something like MIT that works too.

    Thankfully both exist because I think we definitely need both.

    [–] Andromxda@lemmy.dbzer0.com 1 points 2 years ago

    The GPL also makes code available for ANY PURPOSE. It just requires people who modify the code to do the same, which is fair.

    [–] corsicanguppy@lemmy.ca 1 points 8 months ago

    People seem to think that those who choose permissive licences don’t know what they’re doing. Software can be a gift to the world with no strings attached. A company β€œtaking” your code is never taking it away from you, you still have all the code you wrote. Some people want this. MIT is not an incomplete GPL, it has its own reasons.

    As mentioned in another post, I had another motivation for preferring the BSD license over the GPL .

    I maintained a security product for years after the original author left this mature project and focus on life things. In South Korea, 4 engineers used this GPL project internally, but when they went to submit changes back to the project, they were accused and tried for industrial espionage, as the laws in South Korea could be construed to have bearing.

    They lost. They're in jail. The FSF took on their case, but was unable to change that. And, in reality, they were jailed for fulfilling the license requirements.

    Since then, I simply cannot guarantee that people will be free from penalty when following the license terms, and I carry a lot of guilt over it -- it ultimately led to my scaling-back on work and then moving off the project completely. But the code I do write, I prefer the BSD license. I cannot control or predict what people will do, and I certainly cannot control the action of companies when even the FSF can't steer them properly.

    I have no issue with people choosing the GPL; consider it, choose it, support it, that's all good and well and proper. Keep doing that, and were my support ever needed, you'd have it. But my choice is different.

    I got a LOT of flack when I mentioned this before; like I'm some turncoat or cuck and not allowed in the techbro club. And while their opinion is unassailable, its value scales accordingly. Bless their heart.

    [–] HappyFrog@lemmy.blahaj.zone 1 points 2 years ago

    I find MIT to be good for libraries as you can get companies using it and working on it. However, apps and binaries should be copyleft to not get fucked over.

    [–] calcopiritus@lemmy.world 0 points 2 years ago (1 children)

    If I choose MIT it's because I don't care if people "steal" the code. This meme is stupid and condescending, if he didn't mind that Intel used it's code it's because he didn't mind, that why he chose MIT. Why is Intel beating him in the meme? It makes no sense. You are proyecting your thoughts onto him as if that's how he felt, but then you show that he didn't feel the same way you do. Why?

    When I see a GPL license I don't see freedom. I only see forced openness, which makes me immediately avoid that library, since I can't statically link to it.

    Freedom means that everyone can use your code. Yes, that means for-profit corporations. For free, without restrictions.

    If I want to make a piece of software to improve people's lives and I don't care to do it for free, I'll choose MIT. If it gets "stolen" by a for-profit corporation it only makes it better, because now my software has reached more people, thus (theoretically) improving their lives.

    [–] bonnetbee@lemmy.world 1 points 2 years ago (1 children)

    If I want to make a piece of software to improve people's lives

    If that is your intention, GPL would make more sense, as every improvement and development would be forced to be made available to those people, thus helping them further.

    I doubt that your code helps anyone who needs/deserves to be helped, after beeing processed by big corpo.

    You could think about your definition of freedom. For me: My freedom ends, where it restricts others people freedom - I shouldn't be free to rob people and call it restriction if someone forbids this.

    [–] calcopiritus@lemmy.world 0 points 2 years ago (1 children)

    GPL means big corporations just won't use it. If they have to make their software open source, they will just search for an alternative or make their own.

    [–] rglullis@communick.news 1 points 2 years ago

    GPL means big corporations just won’t use it.

    Great. No corporation is working on software for the freedom of its users.

    they will just search for an alternative or make their own.

    Or pay the developer to dual license, which can and should be the preferred way for FOSS developers to fund their work?