paritybit.ca

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

commit 8fced09f6e1b5ea1ec3eb741b02f8c6b9548e3dd
parent 1fe3494a9917e58818ecd52724250343192b3e6e
Author: Jake Bauer <jbauer@paritybit.ca>
Date:   Mon,  8 Nov 2021 03:14:04 -0500

Draft of latest blog post

Diffstat:
Mpages/blog/free-software-is-an-abject-failure.md | 15++++++++-------
1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/pages/blog/free-software-is-an-abject-failure.md b/pages/blog/free-software-is-an-abject-failure.md @@ -471,13 +471,14 @@ have to worry about being sued for an accidental violation of a license that lawyers aren't even confident about getting right. You'll notice that those licenses, however, do not address the issue of -corporations controlling software development, 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't have the resources to -ignore your restrictions or buy your development team. +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't have the resources to ignore your restrictions or buy your development +team. In reality, by licensing your project under the GPL and participating in Free Software culture, instead of limiting the harms that corporations inflict, you