1006
submitted 6 months ago by renzev@lemmy.world to c/linuxmemes@lemmy.world

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.

you are viewing a single comment's thread
view the rest of the comments
[-] snek_boi@lemmy.ml 1 points 6 months ago* (last edited 6 months ago)

There's a fair bit of bias in the terms "restrictive" and "permissive", which make MIT seem like a 'better' choice than a give-and-take license like GPL.

The truth is, MIT is risky for developers. Using just one line from an MIT-licensed project will automatically allow others to exploit your work without giving back. I'd prefer to advocate for balanced licenses that protect both user and developer interests.

[-] lemmynparty 1 points 6 months ago

Ha, maybe I should have licensed my comment.

You’re wrong though.

Using code from an MIT licensed project will not allow others to exploit your work. MIT is compatible with almost all other licenses, so you can incorporate the code without needing to relicense your project.

If you meant that choosing to license your entire project with MIT would allow others to exploit your work, then yes, that’s the whole point of the license.

For some small projects, I’m completely fine with throwing it out into the world with no expectation of anything in return.

If a company ends out using my 50-line file conversion tool in their commercial product, I see that as a bonus thing to put on my résumé.

this post was submitted on 16 Jun 2024
1006 points (88.7% liked)

linuxmemes

21280 readers
885 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