paritybit.ca

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

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

Draft of latest blog post

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

diff --git a/pages/blog/free-software-is-an-abject-failure.md b/pages/blog/free-software-is-an-abject-failure.md @@ -462,8 +462,8 @@ 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 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, you simply have to -copy-paste the copyright and permission notice wherever that code is used. These +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 and 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