1004
submitted 5 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
[-] DreamlandLividity@lemmy.world 0 points 5 months ago

leadership thinks that it is a better

You seem to be having some comprehension issue, that is not what I wrote.

[-] rglullis@communick.news 0 points 5 months ago* (last edited 5 months ago)

So what is your argument? Who is responsible for the decision-making process that leads to "hand writing an inferior solution"? Why do you think that this at all acceptable and reasonable?

You've been writing nothing but opinion-as-fact and resorting to wild rationalizations to justify your preferences, now you want to couch yourself under the questionable ethics of "it's done this way and I can not fight it, so it must be the correct thing to do"?

Let's make a simple test: if you were in charge and had the choice between spending some $$ to dual license a GPL package or to pay for the development of a GPL-only system vs paying $$$$ to do it in-house because you did not find a MIT/BSD package that does what you need, what would you do?

[-] DreamlandLividity@lemmy.world 0 points 5 months ago* (last edited 5 months ago)

I did not write 90% of the things you claim I did. Go make starw-man arguments somewhere else.

[-] rglullis@communick.news 0 points 5 months ago

If you want to talk about fallacies, here are some good examples:

we would just handwrite an inferior solution from scratch rather than handle the bureaucracy.

Bandwagon Fallacy

If it was so much better, that it justified the price, it would outcompete the free one anyway.

Failure to understand basic microeconomics


I did not write 90% of the things you claim I did.

That is true and at the same time does not contradict my point. The whole discussion is about how MIT-style licensing is not as effective for software freedom as GPL licenses. And because you do not have anything to stand on to make an argument against the statement, you keep bringing points that do not address the main issue. When asked directly what you would do, you refuse to give a definite answer.

[-] DreamlandLividity@lemmy.world 0 points 5 months ago* (last edited 5 months ago)

The whole discussion is about how MIT-style licensing is not as effective for software freedom as GPL licenses.

No one else is arguing about that here you 🤡 That's just your straw-man.

this post was submitted on 16 Jun 2024
1004 points (88.6% liked)

linuxmemes

21282 readers
1312 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 1 year ago
    MODERATORS