summaryrefslogtreecommitdiff
path: root/articles/open-source-licenses-literally-are-meme.md
diff options
context:
space:
mode:
Diffstat (limited to 'articles/open-source-licenses-literally-are-meme.md')
-rw-r--r--articles/open-source-licenses-literally-are-meme.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/articles/open-source-licenses-literally-are-meme.md b/articles/open-source-licenses-literally-are-meme.md
index a7af138..105f71f 100644
--- a/articles/open-source-licenses-literally-are-meme.md
+++ b/articles/open-source-licenses-literally-are-meme.md
@@ -9,7 +9,7 @@ Open source licenses are licenses that comply with the Open Source Definition â€
An open source license may be an actual license through the (F)OSS respecting developer's eyes, however other see it as a paperweight instead. Hence, there would be a regular case of [the open source projects on proprietary softwares being sold commercially by tech corpos](https://www.theregister.com/2022/05/16/vizio_gpl_contract/), while the developers of those projects are getting barely any benefit to no benefit from it at all. And as for it being used in proprietary softwares, if it is from a country where the concept of holding an indigenous company accountable is non-existent (*cough cough* China) then forget about seeking any sort of justice you want or worse, if these are guarded by DMCA laws, it would be impossible to actually see if the software does violate the licenses without inviting a class action lawsuit *against* the devs instead, which can be an immediate death sentence (not literally) to the devs.
### Permissive licenses are the absolute worst
-Permissive licenses may sound nice as a concept, (as these licenses give absolute freedom in its usage) in practise this would mean that your project would immediately get copied by the others on whatever they want, whether to use it on a proprietary soywares or not, while giving you very little to no credit at all, as there are 0 safeguards being promised against so. Hence, you can't even give a lawsuit to someone even if you wanted as they still didn't violate the license of your software.
+Permissive licenses may sound nice as a concept, (as these licenses give absolute freedom in its usage) in practise this could mean that your project could immediately get copied by the others on whatever they want, whether to use it on a proprietary soywares or not, while giving you very little to no credit at all, as there are 0 safeguards being promised against so. Hence, you can't even give a lawsuit to someone even if you wanted as they still didn't violate the license of your software.
The meme below perfectly explains the absolute state of these licenses: