diff options
Diffstat (limited to '')
-rw-r--r-- | _articles/2020-11-14-local-first-software-you-own-your-data-in-spite-of-the-cloud-article-review.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/_articles/2020-11-14-local-first-software-you-own-your-data-in-spite-of-the-cloud-article-review.md b/_articles/2020-11-14-local-first-software-you-own-your-data-in-spite-of-the-cloud-article-review.md index 635a9a5..68ae03c 100644 --- a/_articles/2020-11-14-local-first-software-you-own-your-data-in-spite-of-the-cloud-article-review.md +++ b/_articles/2020-11-14-local-first-software-you-own-your-data-in-spite-of-the-cloud-article-review.md @@ -110,15 +110,15 @@ If it stops working due do, say, data growth, what are the options? Reverting to an earlier backup, and making it read-only? That isn't really a "Long Now", but rather a "Long Now as long as the software keeps working as expected". -The point is: if the software isn't free/libre, "The Long Now" isn't achievable +The point is: if the software isn't free, "The Long Now" isn't achievable without a lot of wishful thinking. Maybe the authors were trying to be more -friendly towards business who don't like libre software, but in doing so they've proposed +friendly towards business who don't like free software, but in doing so they've proposed a contradiction by reconciling "The Long Now" with proprietary software. -It isn't the same as saying that any free/libre software achieves that ideal, +It isn't the same as saying that any free software achieves that ideal, either. The license can still be free, but the source code can become unavailable due to cloud rot. Or maybe the build is undocumented, or the build -tools had specific configuration that one has to guess. A piece of free/libre +tools had specific configuration that one has to guess. A piece of free software can still fail to achieve "The Long Now". Being free doesn't guarantee it, just makes it possible. |