this post was submitted on 16 Jun 2024
996 points (88.5% liked)

linuxmemes

21603 readers
801 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 members of the community for any reason.
  • 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.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 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. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    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 fork-bomb your computer.

    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.

    top 50 comments
    sorted by: hot top controversial new old
    [–] [email protected] 214 points 6 months ago (7 children)

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

    [–] [email protected] 93 points 6 months ago (3 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.

    [–] [email protected] 52 points 6 months ago (4 children)

    Not all of us write code simply for monetary gain and some of us have philosophical differences on what you can and should own as far as the public commons goes. And not all of us view closed derivatives as a ontologically bad.

    [–] [email protected] 18 points 6 months ago (1 children)

    And not all of us view closed derivatives as a ontologically bad.

    Please explain how allowing a third-party to limit computer users' ability to control and modify their own property is anything other than ontologically bad?

    [–] [email protected] 23 points 6 months ago (2 children)

    If I release something free of restrictions to the world as a gift, that is my prerogative. And a third party's actions don't affect my ability to do whatever I want with the original code, nor the users of their product's ability to do what they want with my code. And the idea of "property" here is pretty abstract. What is it you own when you purchase software? Certainly not everything. Probably not nothing. But there is a wide swath in between in which reasonable people can disagree.

    If you are an intellectual property abolitionist, I doubt there is much I can say to change your mind.

    load more comments (2 replies)
    load more comments (3 replies)
    [–] [email protected] 15 points 6 months ago* (last edited 6 months ago) (3 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.

    load more comments (3 replies)
    [–] [email protected] 14 points 6 months ago (5 children)

    All my own OSS stuff I always release MIT licensed because I want to be able to use the libraries in my closed source job.

    [–] [email protected] 18 points 6 months ago (2 children)

    Be really careful with this.

    Depending on how you contribute to your OSS code, commits you make on company time are considered property of the company. You could, unknowingly, be forcing your code to be closed source if your company ever decides to make a claim for it.

    I prefer to keep things bifurcated. I never reuse my own library and if I do, I rewrite it whole cloth.

    load more comments (2 replies)
    load more comments (4 replies)
    load more comments (6 replies)
    [–] [email protected] 180 points 6 months ago* (last edited 6 months ago) (5 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."

    [–] [email protected] 63 points 6 months ago (3 children)

    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.

    load more comments (3 replies)
    load more comments (4 replies)
    [–] [email protected] 146 points 6 months ago (3 children)

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

    That's where I stopped reading. 👎

    [–] [email protected] 72 points 6 months ago (1 children)

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

    [–] [email protected] 30 points 6 months ago (1 children)

    I guess they take things seriously even in a linuxmemes community

    load more comments (1 replies)
    [–] [email protected] 39 points 6 months 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.

    load more comments (1 replies)
    load more comments (1 replies)
    [–] [email protected] 89 points 6 months ago* (last edited 6 months ago) (4 children)

    I published some packages under MIT a couple of years ago. It is difficult to understand at first, I was happy with the license because anyone could use it like they want.

    Today, I understand that I want to use GPL. With GPL everyone can use the code like they want and I can use their code like I want.

    load more comments (4 replies)
    [–] [email protected] 86 points 6 months ago (27 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.

    [–] [email protected] 34 points 6 months ago (26 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.

    load more comments (26 replies)
    [–] [email protected] 14 points 6 months ago (1 children)

    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.

    Why not put the code in public domain then? Why MIT?

    [–] [email protected] 26 points 6 months ago* (last edited 6 months ago) (1 children)

    Two reasons:

    1. public domain is not very well legally recognized, so code licensed under MIT is easier to use internationally than code in public domain.
    2. MIT includes disclaimer of liability, which as an author you want just to be safe.
    load more comments (1 replies)
    [–] [email protected] 13 points 6 months ago (6 children)

    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.

    One of the arguments in favor of GPL and other "forced openness" licenses is that users should have the right to understand what their own device is doing. You paid for your computer. You own it. You should dictate how it operates. You should at least have the option of understanding what is being done with your machine and modifying it to fit your needs. Closed source software may provide utility, but it doesn't really further collective knowledge since you're explicitly refusing to publicly release the code, and it provides obscurity for developers to hide undesirable functionality like data collection or more directly malicious activity.

    I'm not personally sure how I feel about that argument myself, but I can at least readily acknowledge it as a valid one whether I agree with the decision to force openness or not.

    load more comments (6 replies)
    load more comments (24 replies)
    [–] [email protected] 68 points 6 months ago* (last edited 6 months ago) (2 children)

    There’s nothing Tanenbaum could do

    Tanenbaum doesn’t seem to mind

    Today OP was very dumb and showed his ignorance of the concept "I do whatever I fucking want." Don't be like OP.

    people regretting releasing their work under a permissive license

    They're free to change the licence of future versions. OP also failed at understanding the concept of licences. He's such a silly moron!

    [–] [email protected] 34 points 6 months ago (4 children)

    They’re free to change the licence of future versions.

    Only if they are still the only contributor. Once you have more contributors, it gets far tougher to change the licence.

    load more comments (4 replies)
    [–] [email protected] 17 points 6 months ago

    They’re free to change the licence of future versions.

    Why do you act like I don't know that? The issue here is that once you realize that the license you chose does not reflect your intentions, the damage has likely already been done. From the article I linked:

    I didn't have the foresight to see this coming. I didn't think people so lacked in the spirit of open source. I wanted to promote community contributions, not to have them monetized by other people who don't even provide the source to their modifications. I wanted to grow the tools as a community, not have closed source forks of them overtake my own open source versions.

    [–] [email protected] 65 points 6 months ago (13 children)

    MIT license is useful for a lot of stuff that is traditionally monetized. Game development tools, for example. I don't think a game engine could become very popular if you had to release your game's source code for free.

    [–] [email protected] 52 points 6 months ago

    Literally every library with any traction in any field is MIT licensed.

    If the scientific python stack was GPL, then industry would have just kept paying for Matlab licenses

    [–] [email protected] 15 points 6 months ago (1 children)

    That's a good point! The FSF also developed LGPL for this reason (their particular example was something like OGG that is meant to displace the proprietary (back then) MP3), but you example with game engines is also a good one!

    load more comments (1 replies)
    load more comments (11 replies)
    [–] [email protected] 51 points 6 months ago (5 children)

    Permissive licenses have their place, a reason Godot engine for games has become appealing is MIT.

    load more comments (5 replies)
    [–] [email protected] 42 points 6 months ago (1 children)

    Are we really going to start this pointless discussion again? They are two licenses with different use cases and different considerations. GPL has a lot more mental overhead to using it, MIT is hands off, both of these aren't inherently invalid.

    Also Tanenbaum in your own link mentions that Intel probably would have just written their own microkernel if need be.

    load more comments (1 replies)
    [–] [email protected] 39 points 6 months ago (2 children)

    AI tools have turned them all into MIT licenses

    [–] [email protected] 23 points 6 months ago

    AI scrapers don't obey any license. They strip copyright information from all the code they take.

    load more comments (1 replies)
    [–] [email protected] 35 points 6 months ago* (last edited 6 months ago) (5 children)

    I could imagine MIT might be interesting for Software released by public institutions, that are meant to be used by the industry in any way they want. Sometimes earning money with your product might even be impossible due to restrictions. So, not really Software released with the FOSS philosophy.

    Otherwise I also never really understood why anyone would use the MIT license.

    [–] [email protected] 25 points 6 months ago (1 children)

    I do exactly this: Write code/frameworks that are used in academic research, which is useful to industry. Once we publish an article, we publish our models open-source under the MIT license. That is because companies that want to use it can then embed our models into their proprietary software, with essentially no strings attached. This gives them an incentive to support our research in terms of collaborative projects, because they see that our research results in stuff they can use.

    If we had used the GPL, our main collaborators would probably not have been interested.

    load more comments (1 replies)
    load more comments (4 replies)
    [–] [email protected] 34 points 6 months ago (14 children)

    The two licenses have distinct use cases, and only overlap for some definitions of "free" software. I also think both the comic artist and OP set up a fallacious argument. I'll add that in no way do I support Intel's shenanigans here.

    The comic author takes one specific case of an MIT licensed product being used in a commercial product, and pits it against another GPL product. This ignores situations where MIT is the right answer, where GPL is the wrong one, situations where legal action on GPL violations has failed, and all cases where the author's intent is considered (Tanenbaum doesn't mind). From that I conclude that this falls under The Cherry Picking Fallacy. While humorous, it's a really bad argument.

    But don't take it from me, learn from the master of logic himself.

    commonly referred to as “cuck licenses”

    This sentiment makes the enclosing sentence an Ad-hominem fallacy, by attacking the would-be MIT license party as having poor morals and/or low social standing. Permissive licenses absolutely do allow others to modify code without limit, but that is suggested to be a bad thing on moral grounds alone. That said, I'd love to see a citation here because that's the first I've heard of this pejorative used to describe software licensing.

    load more comments (14 replies)
    [–] [email protected] 23 points 6 months ago* (last edited 6 months ago) (2 children)

    Controversial opinion: Copyleft is actually more free than permissive licenses.

    Because the way the GPL works is how the world would be if there were no licenses and no copyright at all. Because then anything made public is free to use. And if I were to reverse-engineer a binary then I could still add that code to my software.

    But since we live in a world where we play make-believe that you can make something public and still "own it" at the same time (e.g. copyright) and where using reverse-engineered code can still get you into legal trouble, the GPL is using their own silly logic against them (like fighting fire with fire) to create a bubble of software that acts like a world without any licenses.

    Permissive licenses don't do that, they allow your open software to just get repurposed under a non-free paradigm which could never occur in a world with no licenses. And so ironically permissive licensing in a world that is (artifically) non-permissive by default does not reflect a world with no licenses, and is thus less free than Copyleft.

    load more comments (2 replies)
    [–] [email protected] 17 points 6 months ago (6 children)

    I am a consultant who sometimes writes code to do certain useful things as part of larger systems (parts of which may be commercial or GPL) but my clients always try to impose terms in their contracts with me which say that anything I develop immediately becomes theirs, which limits my ability to use it in my next project. I can to some extent circumvent this if I find a way to publish the work, or some essential part of it, under an MIT license. I'm never going to make money off of my code directly; at best it's middleware, and my competitors don't use the same stack, so I'm not giving them any real advantage... I don't see how I'm sabotaging myself in this situation; if anything the MIT license is a way of securing my freedom and it benefits my future customers as well since I don't have to rebuild from scratch every time.

    load more comments (6 replies)
    [–] [email protected] 17 points 6 months ago (1 children)
    load more comments (1 replies)
    [–] [email protected] 17 points 6 months ago (1 children)

    The MIT is still a free software license. It is completely valid to use it from a Foss perspective.

    load more comments (1 replies)
    [–] [email protected] 15 points 6 months ago* (last edited 6 months ago) (16 children)

    I'm an idiot making a thing, and I need to pick a license. Where's a good place to talk to people more knowledgeable than myself on the subject?

    EDIT: so my thing isn't software, i probably should have mentioned that. I am making a ruleset and setting for something similar to but not exactly a tabletop rpg. The ORC license sounds promising, but the legalese makes my brain gray out. ChatGPT tells me to use a version of the Creative Commons license, but ChatGPT isn't exactly reliable.

    load more comments (16 replies)
    [–] [email protected] 14 points 6 months ago

    Interestingly enough, Tanenbaum doesn’t seem to mind what intel did.

    Yeah, duh. Intelligent people read licenses before they pick one.

    But there are some examples out there of people regretting releasing their work under a permissive license.

    That's like signing a contract before reading it and then complaining that it contains provisions that surprise you when they are enacted. I'm baffled on a regular basis by how many people understand FOSS licenses only on the basis for hearsay, for example when people insist that GPLed source code must be made available free of charge for everyone. The GNU project has a FAQ about the GPL that spells it out that this is not the case and yet hardly anyone discussing FOSS licenses has even read the FAQ.

    load more comments
    view more: next ›