diff options
author | Arnav Bhatt <arnav@ghativega.in> | 2023-04-25 17:01:53 +0530 |
---|---|---|
committer | Arnav Bhatt <arnav@ghativega.in> | 2023-04-25 17:01:53 +0530 |
commit | 30afcece98906530e68c679e3f84e87e01e67407 (patch) | |
tree | 6ca1dff95489a46472d395263b2cf3fa1efd3290 | |
parent | d90ef8272212f486ed07f2e4ee49eb7c5bfb3ac3 (diff) |
changes
-rw-r--r-- | articles/open-source-licenses-literally-are-meme.md | 8 |
1 files changed, 5 insertions, 3 deletions
diff --git a/articles/open-source-licenses-literally-are-meme.md b/articles/open-source-licenses-literally-are-meme.md index 105f71f..50dc50e 100644 --- a/articles/open-source-licenses-literally-are-meme.md +++ b/articles/open-source-licenses-literally-are-meme.md @@ -1,4 +1,4 @@ -Open source licenses literally are meme +Open source licenses sucks Open source licenses are terrible at actually keeping your software safeguard against the usage of it on proprietary softwares, which is the whole point of its existence. @@ -6,7 +6,7 @@ Open source licenses are terrible at actually keeping your software safeguard ag Open source licenses are licenses that comply with the Open Source Definition — in brief, they allow software to be freely used, modified, and shared. These licenses have set of "rules" that ranges from being truly free to use (aka permissive licenses) like [MIT license](https://opensource.org/licenses/MIT) or having copyleft ideologies, i.e., having safeguards to avoid the software being used in a proprietary fashion like [GPLv3](https://www.gnu.org/licenses/gpl-3.0.en.html), the two most common types of open source licenses. ### The issue -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. +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. And as you can guess, these licenses requires some kind of authority for making it relevant at the first place otherwise it is just a digital paperweight. So in essence, they are just like intellectual "properties" but worse in terms of actually safeguarding your software. ### 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 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. @@ -24,7 +24,9 @@ There are still cases of companies [regularly violating the licenses](https://ar ### There is not a real soultion to this Looking through an idealistic manner, one way to fix the copyleft licenses would be to simply make politicians to take these licenses more seriously and to get rid of DMCA all together. However since we are talking about politicians, that's very unlikely. -So what's my solutions to this? Well, I would recommend to at least stick to copyleft licenses and avoiding permissive licenses all together if you don't want to get immediately screwed over by the tech corporations or release your [software as a freeware](https://en.wikipedia.org/wiki/Freeware/) instead. +So what's my solutions to this? Well, I would recommend to at least stick to copyleft licenses if you still want to use an open source license and avoiding permissive licenses all together if you don't want to get immediately screwed over by the tech corporations or release your [software as a freeware](https://en.wikipedia.org/wiki/Freeware/) instead. + +Ultimately, I would prefer that neither intellectual properties nor copyleft licenses to exist in this world but that's also highly unlikely to ever happen as well. ;tags:software open-source rant ;description:FOSS License: The God That Failed. |