paritybit.ca

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | README | LICENSE

commit f3abe3d8bbfdd2b525b0a069b09ca029bf259ec4
parent d9bb48e37bc1f8e1b248d8f2e074fc79548ca842
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Mon,  8 Nov 2021 13:18:36 -0500

Publish new blog post

Diffstat:
Mpages/blog/free-software-is-an-abject-failure.md | 229+++++++++++++++++++++++++++++++++++++++++--------------------------------------
Mpublic/feeds/sitewide-feed.xml | 505+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Mpublic/sitemap.xml | 1+
3 files changed, 624 insertions(+), 111 deletions(-)

diff --git a/pages/blog/free-software-is-an-abject-failure.md b/pages/blog/free-software-is-an-abject-failure.md @@ -8,8 +8,8 @@ <div class="byline"> <b>Written By:</b> Jake Bauer | - <b>Posted:</b> [DATE] | - <b>Last Updated:</b> [DATE] + <b>Posted:</b> 2021-11-08 | + <b>Last Updated:</b> 2021-11-08 </div> <p class="note">I want to preface this by saying that I used to be a staunch @@ -35,12 +35,12 @@ thriving software ecosystem. [Why Software Should Be Free](https://archive.md/ORsof) by Richard Stallman presents an argument against having owners of software and explains the harm -done by obstructing software development through proprietary licensing. It +done by obstructing software development through proprietary licensing. He posits that software with obstructions results in fewer users, the inability for users to fix programs, and the inability of developers to build upon prior knowledge or work. He also states that the justifications one uses for keeping ownership of the software (which he equates with keeping the software -proprietary) are emotional (i.e. "This software is mine, and I wish to control +proprietary) are emotional (i.e. "This software is mine, and I wish to control it") and economical (i.e. "I wish to become wealthy by programming."). He shuns these excuses and spends the rest of the document refuting those excuses and explaining why the existence of proprietary software is bad and why the @@ -50,12 +50,12 @@ However, in nearly every Free Software project which exists today, there is a clear "owner" of the software—someone who is the copyright holder, benevolent dictator for life, or simply _de facto_ leader of the project and through whom all contributions must flow. Whether we're talking about large projects too -large to fork and maintain by anybody but a massive corporation such as the -Linux Kernel (in which Linus still has complete veto power by the way), Qt (in +large to fork and maintain by anybody but large, well-funded groups such as the +Linux kernel (in which Linus still has complete veto power by the way), Qt (in which the company controls the development of the software and simply allows older versions to be used under a free license), or smaller projects which have -simple leaders. As long as there is a "Copyright YYYY" statement, there are one -or more owners to be aware of. +simple leaders. As long as there is a copyright statement, there are one or more +owners to be aware of. Additionally, the [GNU Manifesto](https://archive.md/V14pR), aside from calling the Open Source movement an "amoral approach", goes on to say that GNU "is not @@ -64,10 +64,11 @@ in the public domain" and will have restrictions placed on further modifications given by Stallman being: "I want to make sure that all versions of GNU remain free." With that, Stallman falls upon the same behaviour that he previously shunned in _Why Software Should Be Free_. He uses his emotional attachment to -the software, something he said was an excuse to defend why software has -ownership, to justify his actions. He is effectively saying "this is _my_ -creation, and I wish to control what others can do with it" as well as clearly -assigning an owner to the software. +the software, something he said was an excuse to defend why software has an +owner, to justify his want to control how others can distribute and modify his +code. He is effectively saying "this is _my_ creation, and I wish to control +what others can do with it" as well as clearly assigning an owner to the +software. If software is not in the public domain, then, by definition, it has to have at least one other owner. If Stallman can dictate how others can use his @@ -76,18 +77,19 @@ clearly has an owner. Simply put, Stallman and others in the Free Software community use the exact same excuses criticized in _Why Software Should Be Free_ as justification for -their actions. These systems are used by them in what is deemed the "right" way -while the movement criticizes the way others use them as wrong. GNU, the GPL, -and seemingly the entirety of Free Software as it stands today are all based on -the same premises as proprietary software. +their actions. GNU, the GPL, and seemingly the entirety of Free Software as it +stands today are all based on the same premises as proprietary software. They +use existing copyright systems in what they deem the "right" way while +simultaneously criticizing the way others use them as wrong. To be frank, the Free Software movement comes off as both a "cult of personality"—worshipping Richard Stallman and his teachings, as well as a "cult of ideology"—shunning those who disagree with the manifestos and the "way of life" that the movement espouses to an extreme degree. As long as you, as a -developer, do everything within the framework of the GPL, you are ethical and -good. As soon as you wish to do something outside of this domain, even by using -a more open, permissive license, you are considered unethical. +developer, do everything within the framework of the GPL and the culture of Free +Software, you are ethical and good. As soon as you wish to do something outside +of this domain—even by using a more open, permissive license—you are +considered unethical. In an article where [Linus Torvalds criticizes the GPLv3](https://web.archive.org/web/20211108043329/https://www.linux.com/news/why-torvalds-sitting-out-gplv3-process/), @@ -117,23 +119,23 @@ understand it, unless you are well-educated in "legalese", you probably don't fully understand the true meaning and effect that the words of the license would _actually_ have in court. -Furthermore, the ramifications of the GPL are still not fully understood by even -lawyers themselves. Many large companies will shy away from the GPL simply -because they don't want to take the risk of using GPL-licensed code improperly -and being forced to reveal their proprietary software. While I don't agree with +The ramifications of the GPL are still not even fully understood by lawyers +themselves. Many large companies will shy away from the GPL simply because they +don't want to take the risk of using GPL-licensed code improperly and being +forced to reveal their proprietary software. While I don't agree with proprietary software as a concept, the fact that even lawyers—who are supposed to be expertly trained in the kind of language used in the license—are uneasy about its terms further reinforces just how unapproachable it is to the everyday software developer. GNU and the GPL have done nothing to remove the overhead of considering who owns software. -Further contributing to the overhead imposed by the GPL, since the development -of the GPL is reactionary—that is to say, it's development and growth over time -was in response to discovered workarounds—there is now the extra complication of -the "-or-later/only" clauses. This is a license which has multiple versions -which are **not** backwards compatible. A project licensed under the GPLv2-only -cannot integrate GPLv3-or-later code without being re-licensed as GPLv3. The -Linux kernel is an excellent example of this. +Since the development of the GPL is reactionary—that is to say, its development +and growth over time was in response to discovered workarounds—there is now even +more overhead by way of the extra complication of the "-or-later/only" clauses. +This is a license which has multiple versions which are **not** backwards +compatible. A project licensed under the GPLv2-only cannot integrate +GPLv3-or-later code without being re-licensed as GPLv3. The Linux kernel is an +excellent example of this. Linus Torvalds even [came out strongly against the GPLv3](https://web.archive.org/web/20211108043329/https://www.linux.com/news/why-torvalds-sitting-out-gplv3-process/) @@ -143,7 +145,7 @@ the ultimate power over the GPLv3; all because a manufacturer put Linux in their products and blocked users from running their own modified software on that hardware which, by the way, had absolutely nothing to do with the Linux kernel itself since the bootloader is the software that would stop users from running -some other software. This lead to people thinking that this was basically an +some other software. This led to people thinking that this was basically just an excuse to expand the scope and powers of the GPL over what could be seen as something completely out of the scope of the GPL-licensed software. The move by the FSF, the actions of Stallman, and the "tivoization" rhetoric are even @@ -181,22 +183,22 @@ corporations who freely comply with the GPL, there are plenty more, such as VMWare, who don't comply and yet [don't face consequences](https://web.archive.org/web/20211027160559/https://sfconservancy.org/news/2019/apr/02/vmware-no-appeal/). Even if a lawsuit is successful, it is usually at the cost of [members of the -FOSS community](https://archive.is/lspvL) who burn out or are left disenchanted +FOSS community who burn out](https://archive.is/lspvL) or are left disenchanted by the whole process. Being GPL-licensed also doesn't prevent a project from being bought and therefore having all control handed over to a corporation. This was most recently seen in the [acquisition of Audacity by Muse Group](https://mu.se/newsroom/tpost/6dhedma301-muse-group-acquires-audacity-expanding-c) -in which Muse Group bought the rights to the audacity code and project. (Note -that if software actually didn't have owners, this could not happen.) Users have -since forked the project, but this doesn't necessarily stop something like this -from happening in the future, and certainly doesn't stop it from happening to -other projects. +in which Muse Group bought the rights to the Audacity code and project. (Note +that if this software actually didn't have owners, this could not happen.) Users +have since forked the project, but this doesn't necessarily stop something like +this from happening in the future, and certainly doesn't stop it from happening +to other projects. The GPL-family of licenses attempt to solve a societal problem by restricting the distribution of software in a manner not unlike the so-called [Ethical Software](https://en.wikipedia.org/wiki/Organization_for_Ethical_Source) -movement does. The GPL acts effectively as a proprietary license that allows you -to the things it deems ethical, so long as you abide by the terms of the license +movement. The GPL acts effectively as a proprietary license that allows you to +the things it deems ethical, so long as you abide by the terms of the license with regards to the distribution and re-licensing restrictions. As long as you are in this "club", everything is fine and dandy and you can make your changes and push them to your favourite projects. As soon as you leave this club and @@ -224,8 +226,8 @@ The GNU Manifesto speaks a lot about how: > "Users will no longer be at the mercy of one programmer or company which owns > the sources and is in sole position to make changes." -But a cursory look at the current landscape of so-called Free Software will tell -you that this is simply not the case _at all_. +But a cursory look at the current landscape of Free Software will tell you that +this is simply not the case _at all_. Users are absolutely at the mercy of the maintainers of software projects to integrate their changes in the current landscape of software development, @@ -238,7 +240,7 @@ for those issues to simply go unsolved for many years. A great example of this is the ['Add an "icon view with thumbnails" mode' GNOME issue](https://web.archive.org/web/20210111165221/https://bugzilla.gnome.org/show_bug.cgi?id=141154&) which was opened in 2004 (it's almost old enough to vote!) and is still -not actually fixed despite many users saying how useful it would be to +not actually fixed despite many users expressing how useful it would be to have this feature. Users simply cannot maintain such complex software on their own and, if they @@ -250,43 +252,47 @@ of the project. Software is not yet simple enough for that and GNU and Free Software did nothing to solve this. In fact, it can be argued that they made this worse by contributing to the creation of a culture of "elitists" who expect all the users of their software to have the ability to read code and very -technical discussions or documentation in order to understand problems. +technical discussions or documentation in order to understand and fix problems. If an experienced user does come along and is dis-satisfied with their corporate support forum-like experience, they might be inclined to fork the project. However another very common sight in the Free Software community is to see accusations towards groups or companies who fork projects of making "hostile forks" or committing "theft" of Free Software. For example, Members of the Free -Software community [shunned and criticized a group of -developers](https://web.archive.org/web/20211021085708/https://news.ycombinator.com/item?id=17007834) -forking a Free Software project to extend it for their own needs because of an -unresponsive maintainer while still keeping it under the _same_ license (a -so-called "unethical" Open Source license, no less). +Software community [shunned and criticized the group of developers who forked +Gogs to make +Gitea](https://web.archive.org/web/20211021085708/https://news.ycombinator.com/item?id=17007834) +when they forked a Free Software project to extend it for their own needs +because of an unresponsive maintainer. They even still kept the project under +the _same_ license (an "unethical" Open Source license, no less). If software is not supposed to have an owner, as _Why Software Should Be Free_ advocates, what exactly is being stolen? Why do they, as the creator of some -piece of software, care if some company takes it software and uses it in their -product or makes proprietary modifications with it? _Why Software Should Be -Free_ specifically outs this need to control what happens with one's software as -one of the main justifications for proprietary licensing and something to be -avoided, yet it is seen everywhere in the Free Software culture. In fact, an -article entitled _[Don't fear the fork: How DVCS aids open source +piece of software, care if some company or even another FOSS developer takes it +and uses it in their product or makes proprietary modifications with it? _Why +Software Should Be Free_ specifically outs this need to control what happens +with one's software as one of the main justifications for proprietary licensing +and something to be avoided, yet it is seen everywhere in the Free Software +culture. In fact, an article entitled _[Don't fear the fork: How DVCS aids open +source development](https://web.archive.org/web/20201112014255/https://www.techrepublic.com/blog/linux-and-open-source/dont-fear-the-fork-how-dvcs-aids-open-source-development/)_ perfectly exemplifies how the Free Software culture views forks (of course, it's -written from the perspective of the so-called "unethical" Open Source software). +written from the perspective of "unethical" Open Source movement). The goal of Free Software as laid out by _Why Software Should Be Free_ was to create a world in which there were no owners of software and in which -distribution was not restricted. Yet, despite this, the GPL family of licenses -and the culture of Free Software actively _encourage_ both of those things and +distribution was not restricted. Yet, despite this, the way the GPL family of +licenses puts restrictions on the distribution of GPL-licensed software combined +with the culture of Free Software actively _encourage_ both of those things and actively _discourage_ forking software and modifying it to suit your own needs. -The GPL places strict restrictions on the distribution of GPL-licensed software -and that, plus the culture surrounding Free Software, encourage this structure -of ownership and copyright over the software by the copyright holders. From the -point of view of _Why Software Should Be Free_, the GPL combined with this -culture is, in reality, hardly much better than the world of proprietary +From the point of view of _Why Software Should Be Free_, the GPL combined with +this culture is, in reality, hardly much better than the world of proprietary software we had before. +The degree of openness which exists in the current software landscape can be, to +a large degree, attributed to the Open Source movement. It happened in spite of +the Free Software movement, not because of it. + ### The Failure of Free Software to Remain Relevant Free Software and the surrounding culture and institutions are often viewed as a @@ -328,15 +334,15 @@ App Store. Sure, this isn't a good thing and it can be easily argued that this is unethical because you don't ever own the apps you purchase, however, it is hardly "censoring free software" given that, as the owner of a Free Software project, you can freely submit GPL-licensed software to the App Store and Apple -assumes you have the rights to provide Apple with a non-GPL-licensed build. If +assumes you have the rights to provide them with a non-GPL-licensed build. If you don't have that ability because you don't own exclusive rights to the software and it's not feasible for you to get the permission of every contributor with their name attached to the project, well, that's not Apple's problem. The FSF words their article like Apple is attacking them when, in reality, Apple doesn't care what license you've chosen, only that you grant them the ability to distribute your app under the terms of their EULA. The wording in -that blog post is yet another example of how the FSF are behaving like utter -clowns and why they are seen as a farce. They should know better. +that blog post is yet another example of why the FSF are seen as a farce. They +should know better. This reputation of preferring ideological book-thumping over meaningful action is nothing new. Most who are familiar with Linux are likely familiar with @@ -345,14 +351,14 @@ rant](https://web.archive.org/web/20211102101640/https://www.gnu.org/gnu/linux-a in which he squabbles and nitpicks over the relevancy of GNU to the Linux name. Ignoring that the only significant contributions to the Linux system GNU can claim is the compiler, the coreutils, and the C library. While these used to be -relatively significant in the early 90s, most Linux systems run far more non-GNU -software than GNU software. +relatively significant in the early 90s, most Linux systems today run far more +non-GNU software than GNU software. In fact, even those base GNU components are quickly fading into irrelevancy as projects like Clang/LLVM, rewrites of coreutils to be faster and cleaner (e.g. Busybox or various Rust projects), and other libc's such as muslc are gaining more and more traction each passing day. GNU is simply failing to make any -meaningful and actual progress, and is grasping at the straws in an attempt to +meaningful and actual progress, and is grasping at straws in an attempt to remain relevant. Not only have other projects such as OpenBSD long since abandoned things like modern GCC due to later versions becoming unmaintainable, buggy behemoths, GNU themselves haven't even released their HURD kernel in any @@ -376,21 +382,21 @@ continue, what use even are these institutions? What use is the GPL? Regarding the quality of GNU software, outside of the ~~cult~~ community of Free Software, GNU code has a reputation of being resource-hungry, buggy, bloated, or -annoying and frustrating to work with, as many who use alternative libc's, -compilers, utilities, or programs will attest. GNU creations have a reputation -for being needlessly complex—solving problems which don't really exist in the -first place if you write good software (or documentation)—and having -obtuse source code. The GNU Info system and the code found in many of -the coreutils are good examples of this. - -And finally, we can talk about how the conduct of Richard Stallman himself -reflects on the whole Free Software movement. The Free Software movement went -through its own little "constitutional crisis" over the question of whether or -not to keep him on as the face of Free Software after he made some comments on -an MIT mailing list about a sensitive topic. I won't go into specifics about -that situation here, since it has been covered to death in other media outlets -and can be easily searched for (search "stallman mit mailing list"), but suffice -to say Stallman acted in a completely unprofessional and inept manner. In fact, +annoying and frustrating to work with, as many who have had the pleasure of +using alternative libc's, compilers, utilities, or programs will attest. GNU +creations have a reputation for being needlessly complex—solving problems which +don't really exist in the first place if you write good software (or +documentation)—and having obtuse source code. The GNU Info system and the code +found in many of the coreutils are good examples of this. + +Finally, we can talk about how the conduct of Richard Stallman himself reflects +on the whole Free Software movement. The Free Software movement went through its +own little "constitutional crisis" over the question of whether or not to keep +him on as the face of Free Software after he made some comments on an MIT +mailing list about a sensitive topic. I won't go into specifics about that +situation here, since it has been covered to death in other media outlets and +can be easily searched for (search "stallman mit mailing list"), but, suffice to +say, Stallman acted in a completely unprofessional and inept manner. In fact, that is far from the only example of him behaving in such a way. In 2007, Stallman sent [a message to the OpenBSD-misc mailing @@ -419,27 +425,27 @@ the use of unethical and flawed copyright legislation. It has done very little to prevent corporate takeover of projects, improve the software development landscape, or make the lives of developers or users easier. It has done nothing that more ethical, permissive software licenses and the culture of collaboration -born out of projects such as BSD Unix didn't already do, except create a toxic -subculture of Free Software cult worshippers. - -One cannot solve the copyright, ownership, or distribution problem of software -through playing into the exact same flawed systems that allow such problems to -exist in the first place. This is a problem to solve on a societal level, not on -the level of individual software projects through an obtuse license. It has the -very real effect of restricting innovation, sharing, and collaboration between -developers. - -None of this is to say that proprietary licenses are okay or even that Open -Source is the alternative. In fact, the Open Source Initiative is not all that -much better than the Free Software Foundation, it just has a mostly different -set of problems which are out of scope for this essay. - -For the most part, I agree with _Why Software Should Be Free_. He has perfectly -valid and good ideas in that essay, yet misses the mark with their +born out of projects such as BSD Unix didn't already do, except to create a +toxic subculture of Free Software cult worshippers. + +One cannot solve the copyright, ownership, or restricted distribution problems +of software through playing into the exact same flawed systems that allow such +problems to exist in the first place. These are problems which must be solved on +a societal level, not on the level of individual software projects through an +obtuse license. Free Software, as it stands today, has the very real effect of +restricting innovation, sharing, and collaboration between developers. + +None of this is to say that proprietary licenses are okay or even that the Open +Source movement is the alternative. In fact, the Open Source Initiative is not +all that much better than the Free Software Foundation, it just has a mostly +different set of problems which are out of scope for this essay. + +For the most part, I agree with _Why Software Should Be Free_. Stallman has +perfectly valid and good ideas in that essay, yet he misses the mark with their implementation. I mainly agree with Stallman's points that software should not have owners and that restricting software distribution is unethical. I believe that software shouldn't have owners and nobody should get to control how their -software is used, studied, distributed, hacked upon. +software is used, studied, distributed, or hacked upon. The only licenses which _truly_ meet all these criteria and can be considered ethical are public domain licenses. Licensing your code under [the @@ -447,16 +453,17 @@ Unlicense](https://unlicense.org/), the [0BSD License](https://choosealicense.com/licenses/0bsd/), or the [CC0 License](https://creativecommons.org/share-your-work/public-domain/cc0/) means that you do not place _any_ restrictions on the software whatsoever. People -don't even have to mention your name or your project when they use your code. +don't even have to mention your name or your project when they use your code +because you are no longer the owner of that software. If you do at least wish to have your name attached to the code (something that I personally want if I care about the software I'm writing), commonly used permissive licenses are the best option. Licenses such as the [MIT -License](https://choosealicense.com/licenses/mit/) or, my preferred license, the -[ISC License](https://choosealicense.com/licenses/isc/) impose no further -restrictions other than maintaining a copyright notice for that code used in -other projects. People are free to do whatever they want with your code, so long -as they keep your name on parts that you wrote. +License](https://choosealicense.com/licenses/mit/) or the [ISC +License](https://choosealicense.com/licenses/isc/) (my preferred license) impose +no further restrictions other than maintaining a copyright and permission notice +for that code if used in other projects. People are free to do whatever they +want with your code, so long as they keep your name on parts that you wrote. Not only do these options provide far more _real freedom_ to developers, they remove the overhead of having to think about who owns the software. In the case @@ -464,10 +471,10 @@ of software in the public domain, you don't have to worry at all because there is no owner. In the case of permissively-licensed software, it's a simple matter of copy-pasting the necessary notice(s) wherever that code is used. These licenses are also simple, easy to understand, and the culture surrounding them -is such that you don't have to worry about a mob coming after you for forking -the project and morphing it into something that serves your needs, nor do you -have to worry about being sued for an accidental violation of a license that -lawyers aren't even confident about getting right. +is such that you don't have to worry about a mob coming after you for forking a +project and morphing it into something that serves your needs, nor do you have +to worry about being sued for an accidental violation of a license that even +lawyers aren't confident about getting right. You'll notice that those licenses, however, do not address the issue of corporations controlling software development and distribution, people using diff --git a/public/feeds/sitewide-feed.xml b/public/feeds/sitewide-feed.xml @@ -7,6 +7,511 @@ <description>The feed that covers all notable additions, updates, announcements, and other changes for the entire paritybit.ca website.</description> <item> + <title>Free Software is an Abject Failure</title> + <link>https://www.paritybit.ca/blog/free-software-is-an-abject-failure</link> + <guid>https://www.paritybit.ca/blog/free-software-is-an-abject-failure</guid> + <pubDate>Mon, 08 Nov 2021 13:03:58 -0500</pubDate> + <description><![CDATA[<h2 id="Free%20Software%20is%20an%20Abject%20Failure">Free Software is an Abject Failure</h2> + +<div class="byline"> +<b>Written By:</b> Jake Bauer | + <b>Posted:</b> 2021-11-08 | + <b>Last Updated:</b> 2021-11-08 +</div> + +<p class="note">I want to preface this by saying that I used to be a staunch +software freedom evangelist. I used to license all my works GPLv3-or-later and +CC-BY-SA wherever I could and I used to believe quite strongly in the words of +Richard Stallman. I have since started to think more about the real effects of +the Free Software movement and have changed the way I write and license my +software as a result. I implore you to genuinely consider what I have written in +this post and to approach it with an open mind. Your knee-jerk reaction may be +to reject what I am saying as anti-freedom or pro-corporation but that is not +the case. I simply no longer believe in the Free Software movement.</p> + +<p>Free Software is an abject failure. It may sound like a good concept on its +face—especially with the kind of language often used to describe the movement +and its opponents—but, when put under scrutiny, the institutions and practices +that make up the Free Software movement fundamentally fail at their stated +goals. Free Software is an ideological mess, Free Software hampers +collaboration, Free Software is legally ineffective, Free Software makes the +lives of developers harder, and Free Software fundamentally gets in the way of a +thriving software ecosystem.</p> + +<h3 id="The%20Failure%20of%20the%20Free%20Software%20Ideology">The Failure of the Free Software Ideology</h3> + +<p><a href="https://archive.md/ORsof">Why Software Should Be Free</a> by Richard Stallman +presents an argument against having owners of software and explains the harm +done by obstructing software development through proprietary licensing. He +posits that software with obstructions results in fewer users, the inability for +users to fix programs, and the inability of developers to build upon prior +knowledge or work. He also states that the justifications one uses for keeping +ownership of the software (which he equates with keeping the software +proprietary) are emotional (i.e. &#8220;This software is mine, and I wish to control +it&#8221;) and economical (i.e. &#8220;I wish to become wealthy by programming.&#8221;). He shuns +these excuses and spends the rest of the document refuting those excuses and +explaining why the existence of proprietary software is bad and why the +alternative—software not having owners—is better.</p> + +<p>However, in nearly every Free Software project which exists today, there is a +clear &#8220;owner&#8221; of the software—someone who is the copyright holder, benevolent +dictator for life, or simply <em>de facto</em> leader of the project and through whom +all contributions must flow. Whether we&#8217;re talking about large projects too +large to fork and maintain by anybody but large, well-funded groups such as the +Linux kernel (in which Linus still has complete veto power by the way), Qt (in +which the company controls the development of the software and simply allows +older versions to be used under a free license), or smaller projects which have +simple leaders. As long as there is a copyright statement, there are one or more +owners to be aware of.</p> + +<p>Additionally, the <a href="https://archive.md/V14pR">GNU Manifesto</a>, aside from calling +the Open Source movement an &#8220;amoral approach&#8221;, goes on to say that GNU &#8220;is not +in the public domain&#8221; and will have restrictions placed on further modifications +(in the form of disallowing proprietary modifications), with the justification +given by Stallman being: &#8220;I want to make sure that all versions of GNU remain +free.&#8221; With that, Stallman falls upon the same behaviour that he previously +shunned in <em>Why Software Should Be Free</em>. He uses his emotional attachment to +the software, something he said was an excuse to defend why software has an +owner, to justify his want to control how others can distribute and modify his +code. He is effectively saying &#8220;this is <em>my</em> creation, and I wish to control +what others can do with it&#8221; as well as clearly assigning an owner to the +software.</p> + +<p>If software is not in the public domain, then, by definition, it has to have at +least one other owner. If Stallman can dictate how others can use his +software—even if it is more freely than most proprietary software—then it +clearly has an owner.</p> + +<p>Simply put, Stallman and others in the Free Software community use the exact +same excuses criticized in <em>Why Software Should Be Free</em> as justification for +their actions. GNU, the GPL, and seemingly the entirety of Free Software as it +stands today are all based on the same premises as proprietary software. They +use existing copyright systems in what they deem the &#8220;right&#8221; way while +simultaneously criticizing the way others use them as wrong.</p> + +<p>To be frank, the Free Software movement comes off as both a &#8220;cult of +personality"—worshipping Richard Stallman and his teachings, as well as a &#8220;cult +of ideology"—shunning those who disagree with the manifestos and the &#8220;way of +life&#8221; that the movement espouses to an extreme degree. As long as you, as a +developer, do everything within the framework of the GPL and the culture of Free +Software, you are ethical and good. As soon as you wish to do something outside +of this domain—even by using a more open, permissive license—you are +considered unethical.</p> + +<p>In an article where <a href="https://web.archive.org/web/20211108043329/https://www.linux.com/news/why-torvalds-sitting-out-gplv3-process/">Linus Torvalds criticizes the +GPLv3</a>, +Torvalds even says:</p> + +<blockquote> +<p>&#8220;I think the GPLv3 is expressly designed to not allow [the meeting between +open source and free software people]. Exactly because the FSF considers us +open source people &#8216;heretics.&#8217;&#8221;</p> +</blockquote> + +<h3 id="The%20Failure%20of%20the%20GPL">The Failure of the GPL</h3> + +<p>One of the stated goals written in the GNU Manifesto is:</p> + +<blockquote> +<p>&#8220;Finally, the overhead of considering who owns the system software and what +one is or is not entitled to do with it will be lifted.&#8221;</p> +</blockquote> + +<p>One look at the GPL will tell you that they have utterly failed at this. The +GPL, especially with version 3, has become so complicated that only a programmer +with relatively advanced legal knowledge and ability to read <em>and properly +understand</em> &#8220;legalese&#8221; will be able to decipher it to know what they are able +and unable to do with it. There exist websites which explain the license in +plain English, but even those say their explanations are no substitute for +reading the license. This is because of the very specific meaning that many of +the words in the license take on when put in the context of our modern legal +system. So, while you may be able to read the GPL and <em>think</em> that you +understand it, unless you are well-educated in &#8220;legalese&#8221;, you probably don&#8217;t +fully understand the true meaning and effect that the words of the license would +<em>actually</em> have in court.</p> + +<p>The ramifications of the GPL are still not even fully understood by lawyers +themselves. Many large companies will shy away from the GPL simply because they +don&#8217;t want to take the risk of using GPL-licensed code improperly and being +forced to reveal their proprietary software. While I don&#8217;t agree with +proprietary software as a concept, the fact that even lawyers—who are supposed +to be expertly trained in the kind of language used in the license—are uneasy +about its terms further reinforces just how unapproachable it is to the everyday +software developer. GNU and the GPL have done nothing to remove the overhead of +considering who owns software.</p> + +<p>Since the development of the GPL is reactionary—that is to say, its development +and growth over time was in response to discovered workarounds—there is now even +more overhead by way of the extra complication of the &#8220;-or-later&#47;only&#8221; clauses. +This is a license which has multiple versions which are <strong>not</strong> backwards +compatible. A project licensed under the GPLv2-only cannot integrate +GPLv3-or-later code without being re-licensed as GPLv3. The Linux kernel is an +excellent example of this.</p> + +<p>Linus Torvalds even <a href="https://web.archive.org/web/20211108043329/https://www.linux.com/news/why-torvalds-sitting-out-gplv3-process/">came out strongly against the +GPLv3</a> +and the process by which the FSF created the license. Many others in the +industry also saw this as an extreme and unnecessary move by the FSF to wield +the ultimate power over the GPLv3; all because a manufacturer put Linux in their +products and blocked users from running their own modified software on that +hardware which, by the way, had absolutely nothing to do with the Linux kernel +itself since the bootloader is the software that would stop users from running +some other software. This led to people thinking that this was basically just an +excuse to expand the scope and powers of the GPL over what could be seen as +something completely out of the scope of the GPL-licensed software. The move by +the FSF, the actions of Stallman, and the &#8220;tivoization&#8221; rhetoric are even +<a href="https://web.archive.org/web/20211020102058/https://sfconservancy.org/blog/2021/jul/23/tivoization-and-the-gpl-right-to-install/">heavily criticized by Software Freedom Conservancy member Bradley M. +Kuhn</a>.</p> + +<p>Putting aside the political manoeuvrings of the FSF, the mere existence of an +&#8220;-or-later&#8221; clause is a ridiculous thing to attach to a license. Anybody who +licenses their project under a GPLv3-or-later license puts a lot of trust in the +stewards of the GPL that the next version of the GPL will align with their +values and goals; a GPLv3-or-later project will be able to be licensed under a +GPLv4 license whatever the clauses of that GPLv4 license. This is a lot of stock +to put into a group of people like the FSF who were so dogmatic and exclusionary +in their development of the GPLv3.</p> + +<p>The reality of the GPL is that there is still a lot of overhead in considering +who owns the software. Not only in whether or not a developer should choose +version 2 or version 3 of the license depending on their goals, but also for +developers and users alike who try to understand the language of the license to +determine what they can do with the software and, if they are integrating some +GPL-licensed code into their own product, who actually owns and has copyright +over that software.</p> + +<p>Those who wish to integrate GPL-licensed code into their otherwise +non-GPL-licensed projects are faced with the decision to relicense their code +under the GPL, remake the functionality of the library under a more open +license, or otherwise abandon those efforts altogether. While the GPL may +&#8220;prevent&#8221; corporations or people from taking GPL-licensed code and integrating +it into a proprietary product, it also prevents literally any other +non-GPL-licensed project from using GPL-licensed code, even other FOSS projects.</p> + +<p>Even so, it&#8217;s not like the GPL actually prevents corporations from stealing +GPL-licensed code and integrating it into projects. While there are plenty of +corporations who freely comply with the GPL, there are plenty more, such as +VMWare, who don&#8217;t comply and yet <a href="https://web.archive.org/web/20211027160559/https://sfconservancy.org/news/2019/apr/02/vmware-no-appeal/">don&#8217;t face +consequences</a>. +Even if a lawsuit is successful, it is usually at the cost of <a href="https://archive.is/lspvL">members of the +FOSS community who burn out</a> or are left disenchanted +by the whole process. Being GPL-licensed also doesn&#8217;t prevent a project from +being bought and therefore having all control handed over to a corporation. This +was most recently seen in the <a href="https://mu.se/newsroom/tpost/6dhedma301-muse-group-acquires-audacity-expanding-c">acquisition of Audacity by Muse +Group</a> +in which Muse Group bought the rights to the Audacity code and project. (Note +that if this software actually didn&#8217;t have owners, this could not happen.) Users +have since forked the project, but this doesn&#8217;t necessarily stop something like +this from happening in the future, and certainly doesn&#8217;t stop it from happening +to other projects.</p> + +<p>The GPL-family of licenses attempt to solve a societal problem by restricting +the distribution of software in a manner not unlike the so-called <a href="https://en.wikipedia.org/wiki/Organization_for_Ethical_Source">Ethical +Software</a> +movement. The GPL acts effectively as a proprietary license that allows you to +the things it deems ethical, so long as you abide by the terms of the license +with regards to the distribution and re-licensing restrictions. As long as you +are in this &#8220;club&#8221;, everything is fine and dandy and you can make your changes +and push them to your favourite projects. As soon as you leave this club and +want to pull code from a GPL-licensed project into your MIT-licensed project, +well, sorry, too bad for you.</p> + +<p>While the GPL may not cause as much of an obstruction or be as unethical as +proprietary software, it is frankly not that much better. It causes distress and +conflict in the software community, is difficult for non-lawyers to fully +understand, and harms developers of non-GPL-licensed FOSS software. It is, for +example, the reason why the BSDs cannot take improvements made in the Linux +kernel and directly integrate them into their own kernels and <a href="https://web.archive.org/web/20211026123333/https://itsfoss.com/linus-torvalds-zfs/">it is the reason +why ZFS cannot be integrated into the Linux +kernel</a>, +but can be shipped with FreeBSD.</p> + +<p>For all this talk of Free Software being the ethical option and the GPL being +the ultimate defender of user and developer rights, it completely goes against +the ethical principles laid out in <em>Why Software Should Be Free</em>. So much for &#8220;free as in freedom&#8221;.</p> + +<h3 id="The%20Failure%20of%20the%20Free%20Software%20Culture">The Failure of the Free Software Culture</h3> + +<p>The GNU Manifesto speaks a lot about how:</p> + +<blockquote> +<p>&#8220;Users will no longer be at the mercy of one programmer or company which owns +the sources and is in sole position to make changes.&#8221;</p> +</blockquote> + +<p>But a cursory look at the current landscape of Free Software will tell you that +this is simply not the case <em>at all</em>.</p> + +<p>Users are absolutely at the mercy of the maintainers of software projects to +integrate their changes in the current landscape of software development, +especially with software projects as complicated as a many of the popular GUI +toolkits, kernels, or desktop environments. In fact, Free Software project issue +boards and forums are, in reality, not much better than corporate support +forums. Often when one opens an issue in a large software project it can take +months or even years for those issues to be worked out. It&#8217;s also not uncommon +for those issues to simply go unsolved for many years. A great example of this +is the <a href="https://web.archive.org/web/20210111165221/https://bugzilla.gnome.org/show_bug.cgi?id=141154&amp;">&#8216;Add an &#8220;icon view with thumbnails&#8221; mode&#8217; GNOME +issue</a> +which was opened in 2004 (it&#8217;s almost old enough to vote!) and is still +not actually fixed despite many users expressing how useful it would be to +have this feature.</p> + +<p>Users simply cannot maintain such complex software on their own and, if they +have limited programming ability, cannot be expected fork a project, make their +fix, test their fix, act on feedback from the maintainers (if they&#8217;re lucky +enough to get their patch or pull request noticed), and so on. The current +software development ecosystem makes this impossible, regardless of the license +of the project. Software is not yet simple enough for that and GNU and Free +Software did nothing to solve this. In fact, it can be argued that they made +this worse by contributing to the creation of a culture of &#8220;elitists&#8221; who expect +all the users of their software to have the ability to read code and very +technical discussions or documentation in order to understand and fix problems.</p> + +<p>If an experienced user does come along and is dis-satisfied with their corporate +support forum-like experience, they might be inclined to fork the project. +However another very common sight in the Free Software community is to see +accusations towards groups or companies who fork projects of making &#8220;hostile +forks&#8221; or committing &#8220;theft&#8221; of Free Software. For example, Members of the Free +Software community <a href="https://web.archive.org/web/20211021085708/https://news.ycombinator.com/item?id=17007834">shunned and criticized the group of developers who forked +Gogs to make +Gitea</a> +when they forked a Free Software project to extend it for their own needs +because of an unresponsive maintainer. They even still kept the project under +the <em>same</em> license (an &#8220;unethical&#8221; Open Source license, no less).</p> + +<p>If software is not supposed to have an owner, as <em>Why Software Should Be Free</em> +advocates, what exactly is being stolen? Why do they, as the creator of some +piece of software, care if some company or even another FOSS developer takes it +and uses it in their product or makes proprietary modifications with it? <em>Why +Software Should Be Free</em> specifically outs this need to control what happens +with one&#8217;s software as one of the main justifications for proprietary licensing +and something to be avoided, yet it is seen everywhere in the Free Software +culture. In fact, an article entitled <em><a href="https://web.archive.org/web/20201112014255/https://www.techrepublic.com/blog/linux-and-open-source/dont-fear-the-fork-how-dvcs-aids-open-source-development/">Don&#8217;t fear the fork: How DVCS aids open +source +development</a></em> +perfectly exemplifies how the Free Software culture views forks (of course, it&#8217;s +written from the perspective of &#8220;unethical&#8221; Open Source movement).</p> + +<p>The goal of Free Software as laid out by <em>Why Software Should Be Free</em> was to +create a world in which there were no owners of software and in which +distribution was not restricted. Yet, despite this, the way the GPL family of +licenses puts restrictions on the distribution of GPL-licensed software combined +with the culture of Free Software actively <em>encourage</em> both of those things and +actively <em>discourage</em> forking software and modifying it to suit your own needs. +From the point of view of <em>Why Software Should Be Free</em>, the GPL combined with +this culture is, in reality, hardly much better than the world of proprietary +software we had before.</p> + +<p>The degree of openness which exists in the current software landscape can be, to +a large degree, attributed to the Open Source movement. It happened in spite of +the Free Software movement, not because of it.</p> + +<h3 id="The%20Failure%20of%20Free%20Software%20to%20Remain%20Relevant">The Failure of Free Software to Remain Relevant</h3> + +<p>Free Software and the surrounding culture and institutions are often viewed as a +farce outside of the dedicated Free Software <del>cult</del> community. The FSF has +been slowly descending into irrelevancy for the past two decades as they +struggle to do anything meaningful with their time and resources; instead +favouring to make a lot of unproductive noise. Take, as recent examples, how +they <a href="https://web.archive.org/web/20210605120216/https://www.fsf.org/blogs/community/why-freeing-windows-7-opens-doors">mailed a hard drive to Microsoft telling them to put the Windows 7 source +code on +it</a>, +or how they <a href="https://web.archive.org/web/20211011152025/https://www.fsf.org/campaigns/apple">accuse Apple of &#8220;censoring free +software&#8221;</a> +—despite the fact that Apple isn&#8217;t actually censoring anything and plenty of +Free Software projects such as <a href="https://telegram.org/apps#source-code">Telegram</a> +are <a href="https://apps.apple.com/us/app/telegram-messenger/id686449807">on the App +Store</a>—and also +criticizing them for not supporting their specific chosen free media codecs—once +again, ignoring the plenty of other free media codecs which are otherwise +perfectly supported.</p> + +<p>To expand on that last point about Free Software projects on the App Store, the +<a href="https://web.archive.org/web/20211102184229/https://www.apple.com/legal/internet-services/itunes/dev/stdeula/">Apple App Store +EULA</a> +contains restrictions that the GPL doesn&#8217;t allow (see section 10 of the GPLv3 +and section 6 of the GPLv2). It says:</p> + +<blockquote> +<p>Except as provided in the Usage Rules, you may not distribute or make the +Licensed Application available over a network where it could be used by +multiple devices at the same time. You may not transfer, redistribute or +sublicense the Licensed Application [&#8230;] You may not copy (except as +permitted by this license and the Usage Rules), reverse-engineer, disassemble, +attempt to derive the source code of, modify, or create derivative works of +the Licensed Application, any updates, or any part thereof&#8230;</p> +</blockquote> + +<p>Note that this only applies to the application you purchased in the App store, +as bundled by the App Store. It doesn&#8217;t prevent you from going to GitHub and +modifying the software there, only modifying the software you got from the Apple +App Store. Sure, this isn&#8217;t a good thing and it can be easily argued that this +is unethical because you don&#8217;t ever own the apps you purchase, however, it is +hardly &#8220;censoring free software&#8221; given that, as the owner of a Free Software +project, you can freely submit GPL-licensed software to the App Store and Apple +assumes you have the rights to provide them with a non-GPL-licensed build. If +you don&#8217;t have that ability because you don&#8217;t own exclusive rights to the +software and it&#8217;s not feasible for you to get the permission of every +contributor with their name attached to the project, well, that&#8217;s not Apple&#8217;s +problem. The FSF words their article like Apple is attacking them when, in +reality, Apple doesn&#8217;t care what license you&#8217;ve chosen, only that you grant them +the ability to distribute your app under the terms of their EULA. The wording in +that blog post is yet another example of why the FSF are seen as a farce. They +should know better.</p> + +<p>This reputation of preferring ideological book-thumping over meaningful action +is nothing new. Most who are familiar with Linux are likely familiar with +Richard Stallman&#8217;s <a href="https://web.archive.org/web/20211102101640/https://www.gnu.org/gnu/linux-and-gnu.html">&#8220;GNU+Linux&#8221; +rant</a> +in which he squabbles and nitpicks over the relevancy of GNU to the Linux name. +Ignoring that the only significant contributions to the Linux system GNU can +claim is the compiler, the coreutils, and the C library. While these used to be +relatively significant in the early 90s, most Linux systems today run far more +non-GNU software than GNU software.</p> + +<p>In fact, even those base GNU components are quickly fading into irrelevancy as +projects like Clang&#47;LLVM, rewrites of coreutils to be faster and cleaner (e.g. +Busybox or various Rust projects), and other libc&#8217;s such as muslc are gaining +more and more traction each passing day. GNU is simply failing to make any +meaningful and actual progress, and is grasping at straws in an attempt to +remain relevant. Not only have other projects such as OpenBSD long since +abandoned things like modern GCC due to later versions becoming unmaintainable, +buggy behemoths, GNU themselves haven&#8217;t even released their HURD kernel in any +meaningful capacity despite promising to create such a thing since <em>before Linux +existed</em>.</p> + +<p>Speaking of fading into irrelevancy, many of the Free Software institutions such +as the Software Freedom Conservancy and Free Software Foundation Europe have +been reliant on GPL violation lawsuits as pretty much their sole means to exist. +It has gotten so bad that <a href="https://lwn.net/Articles/873415/">the SFC have tried to bring lawsuits on behalf of the +users of GPL software</a>; something which has +little basis in actual copyright law, but is the only option they have left when +companies either skillfully hide their GPL violations or the owners of GPL +software are unwilling to enforce their license against large opponents. No +wonder these institutions also tend to only go after small opponents from which +they can easily make money. Even very public <a href="https://web.archive.org/web/20211108073317/https://github.com/OnePlusOSS/android_kernel_oneplus_sm8150/issues/13">violations such as those committed +by +OnePlus</a> +have still gone unanswered for. If such violations are clearly allowed to +continue, what use even are these institutions? What use is the GPL?</p> + +<p>Regarding the quality of GNU software, outside of the <del>cult</del> community of Free +Software, GNU code has a reputation of being resource-hungry, buggy, bloated, or +annoying and frustrating to work with, as many who have had the pleasure of +using alternative libc&#8217;s, compilers, utilities, or programs will attest. GNU +creations have a reputation for being needlessly complex—solving problems which +don&#8217;t really exist in the first place if you write good software (or +documentation)—and having obtuse source code. The GNU Info system and the code +found in many of the coreutils are good examples of this.</p> + +<p>Finally, we can talk about how the conduct of Richard Stallman himself reflects +on the whole Free Software movement. The Free Software movement went through its +own little &#8220;constitutional crisis&#8221; over the question of whether or not to keep +him on as the face of Free Software after he made some comments on an MIT +mailing list about a sensitive topic. I won&#8217;t go into specifics about that +situation here, since it has been covered to death in other media outlets and +can be easily searched for (search &#8220;stallman mit mailing list&#8221;), but, suffice to +say, Stallman acted in a completely unprofessional and inept manner. In fact, +that is far from the only example of him behaving in such a way.</p> + +<p>In 2007, Stallman sent <a href="https://marc.info/?l=openbsd-misc&amp;m=119730630513821&amp;w=2">a message to the OpenBSD-misc mailing +list</a> entitled <em>&#8220;Real +men don&#8217;t attack straw men&#8221;</em> in which he accuses the OpenBSD folk of making +straw-man arguments about himself, and then using those arguments to attack his +credibility. If you read through this mailing list thread, you don&#8217;t have to go +far to realize that Stallman has absolutely no clue what he&#8217;s talking about. He +bases his opinion of OpenBSD on &#8220;what I have heard&#8221; and presumes that the +OpenBSD folk care whether or not he recommends their system. He proceeds to have +everything he said get taken apart by the replies which point out all the +inconsistencies in his own arguments and stances.</p> + +<p>After seeing just how ineffective this culture is at advocating for and +enforcing its principles in a meaningful way, as well as seeing the conduct of +one of its top-most members, how could anyone view this as a movement to be +appreciated, let alone joined and celebrated?</p> + +<h3 id="Where%20Do%20We%20Go%20From%20Here?">Where Do We Go From Here?</h3> + +<p>I think, by now, it is accurate to say that Free Software is an abject failure.</p> + +<p>It has failed at its stated goals through both the licenses and the culture it +has created and has instead perpetuated the paradigm of software ownership and +the use of unethical and flawed copyright legislation. It has done very little +to prevent corporate takeover of projects, improve the software development +landscape, or make the lives of developers or users easier. It has done nothing +that more ethical, permissive software licenses and the culture of collaboration +born out of projects such as BSD Unix didn&#8217;t already do, except to create a +toxic subculture of Free Software cult worshippers.</p> + +<p>One cannot solve the copyright, ownership, or restricted distribution problems +of software through playing into the exact same flawed systems that allow such +problems to exist in the first place. These are problems which must be solved on +a societal level, not on the level of individual software projects through an +obtuse license. Free Software, as it stands today, has the very real effect of +restricting innovation, sharing, and collaboration between developers.</p> + +<p>None of this is to say that proprietary licenses are okay or even that the Open +Source movement is the alternative. In fact, the Open Source Initiative is not +all that much better than the Free Software Foundation, it just has a mostly +different set of problems which are out of scope for this essay.</p> + +<p>For the most part, I agree with <em>Why Software Should Be Free</em>. Stallman has +perfectly valid and good ideas in that essay, yet he misses the mark with their +implementation. I mainly agree with Stallman&#8217;s points that software should not +have owners and that restricting software distribution is unethical. I believe +that software shouldn&#8217;t have owners and nobody should get to control how their +software is used, studied, distributed, or hacked upon.</p> + +<p>The only licenses which <em>truly</em> meet all these criteria and can be considered +ethical are public domain licenses. Licensing your code under <a href="https://unlicense.org/">the +Unlicense</a>, the <a href="https://choosealicense.com/licenses/0bsd/">0BSD +License</a>, or the <a href="https://creativecommons.org/share-your-work/public-domain/cc0/">CC0 +License</a> means +that you do not place <em>any</em> restrictions on the software whatsoever. People +don&#8217;t even have to mention your name or your project when they use your code +because you are no longer the owner of that software.</p> + +<p>If you do at least wish to have your name attached to the code (something that I +personally want if I care about the software I&#8217;m writing), commonly used +permissive licenses are the best option. Licenses such as the <a href="https://choosealicense.com/licenses/mit/">MIT +License</a> or the <a href="https://choosealicense.com/licenses/isc/">ISC +License</a> (my preferred license) impose +no further restrictions other than maintaining a copyright and permission notice +for that code if used in other projects. People are free to do whatever they +want with your code, so long as they keep your name on parts that you wrote.</p> + +<p>Not only do these options provide far more <em>real freedom</em> to developers, they +remove the overhead of having to think about who owns the software. In the case +of software in the public domain, you don&#8217;t have to worry at all because there +is no owner. In the case of permissively-licensed software, it&#8217;s a simple matter +of copy-pasting the necessary notice(s) wherever that code is used. These +licenses are also simple, easy to understand, and the culture surrounding them +is such that you don&#8217;t have to worry about a mob coming after you for forking a +project and morphing it into something that serves your needs, nor do you have +to worry about being sued for an accidental violation of a license that even +lawyers aren&#8217;t confident about getting right.</p> + +<p>You&#8217;ll notice that those licenses, however, do not address the issue of +corporations controlling software development and distribution, people using +software in ways you may deem bad or harmful, or the existence of megasoftware. +This is because those are problems that cannot be solved or even effectively +addressed by software licensing. These are societal problems that must be +tackled on a societal level. Attempting to do otherwise simply harms and +imposes more restrictions on small teams, independent developers, and hobbyists +who don&#8217;t have the resources to ignore your restrictions or buy your development +team.</p> + +<p>In reality, by licensing your project under the GPL and participating in Free +Software culture, instead of limiting the harms that corporations inflict, you +end up limiting the good that the rest of us can do. Free Software has failed.</p> + +<p class="note">If this post intrigued you and made you want to learn more, +consider checking out <a +href="https://unixsheikh.com/articles/the-problems-with-the-gpl.html">The +problems with the GPL</a> as well as <a href="/a-critique-of-free-software">A +Critique of Free Software</a> both of which inspired this post.</p>]]></description> + </item> +<item> <title>A Git Workflow With Claws Mail</title> <link>https://www.paritybit.ca/blog/a-git-workflow-with-claws-mail</link> <guid>https://www.paritybit.ca/blog/a-git-workflow-with-claws-mail</guid> diff --git a/public/sitemap.xml b/public/sitemap.xml @@ -3,6 +3,7 @@ <url><loc>https://www.paritybit.ca</loc></url> <url><loc>https://www.paritybit.ca/home</loc></url> <url><loc>https://www.paritybit.ca/blog</loc></url> + <url><loc>https://www.paritybit.ca/blog/free-software-is-an-abject-failure</loc></url> <url><loc>https://www.paritybit.ca/blog/a-git-workflow-with-claws-mail</loc></url> <url><loc>https://www.paritybit.ca/blog/laptops-suck-why-i-might-get-a-macbook-air</loc></url> <url><loc>https://www.paritybit.ca/blog/mastodon-is-dead-long-live-misskey</loc></url> <url><loc>https://www.paritybit.ca/blog/migrating-from-nginx-to-openbsd-httpd-and-relayd</loc></url> <url><loc>https://www.paritybit.ca/blog/flip-phone-challenge-complete</loc></url> <url><loc>https://www.paritybit.ca/blog/flip-phone-challenge</loc></url>