We are still actively working on the spam issue.
Difference between revisions of "Cuck license"
m (Update lukesmith link) |
m (Improved the wording of the first sentence, there's not just one MIT license and there are many BSD licenses) |
||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | A '''Cuck License''' is a permissive software license that that does not | + | A '''Cuck License''' is a permissive software license that that does not ensure the freedom of the user by requiring that derivative works remain free. 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 | + | Examples of Cuck Licenses are the MIT expat license and the BSD licenses ({3,4,2,1,0}-clause are the most common versions). |
| − | == Cuck 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: | 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: | ||
<pre> | <pre> | ||
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. | 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. | ||
</pre> | </pre> | ||
| − | + | However, Tanenbaum maintains that he made the correct choice licensing MINIX under the 3-clause BSD License. | |
== 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]] | ||
Latest revision as of 02:32, 25 March 2024
A Cuck License is a permissive software license that that does not ensure the freedom of the user by requiring that derivative works remain free. 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 expat license and the BSD licenses ({3,4,2,1,0}-clause are the most common versions).
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.
