We are still actively working on the spam issue.
Difference between revisions of "Cuck license"
(→Cuck License backfiring: Rename section, add Tanenbaum's views) |
TheBasedMan (talk | contribs) |
||
| Line 11: | Line 11: | ||
== External links == | == External links == | ||
| − | * [https://lukesmith.xyz/articles/why-i-use-the-gpl-and-not-cuck-licenses Why I use the GPL and not Cuck Licenses] on lukesmith.xyz | + | * [https://lukesmith.xyz/articles/why-i-use-the-gpl-and-not-cuck-licenses Why I use the GPL and not Cuck Licenses] on [[Luke Smith|lukesmith.xyz]] |
[[Category:Licenses]] | [[Category:Licenses]] | ||
Revision as of 08:17, 10 December 2023
A Cuck License is a permissive software license that that does not enforce the freedom of derivative works. This means that anyone can take software licensed under a Cuck License and turn it into proprietary software, effectively cucking the original author.
Examples of Cuck Licenses are the MIT license and BSD license.
Cuck License consequences
There have been instances where developers's usage of Cuck Licenses has backfired. One notable example is Andrew Tanenbaum' MINIX, which got taken by Intel and turned into spyware called the Intel Management Engine. Tanenbaum went on to say:
Many people (including me) don't like the idea of an all-powerful management engine in there at all (since it is a possible security hole and a dangerous idea in the first place), but that is Intel's business decision and a separate issue from the code it runs. A company as big as Intel could obviously write its own OS if it had to.
However, Tanenbaum maintains that he made the correct choice licensing MINIX under the 3-clause BSD License.
