commit 2ee5cbff9c42fb9b10b1ecaa95398b7e9cd323cc
parent 916549d66d52d1960a9484d7d3c3be0a9d8d9359
Author: Ville-Matias Heikkila <viznut@low.fi>
Date: Thu, 16 Jun 2022 15:21:12 +0300
Merge branch 'master' of bleu255.com:/var/www/git.bleu255.com/repos/permacomputing
Diffstat:
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/WWW.mdwn b/WWW.mdwn
@@ -21,7 +21,7 @@ offline, there's no backup plan for locating the files elsewhere.
The design thus discourages small and temporary servers while encouraging
large and centralized servers that maximize their availability. The design
-also discourages local copies and mirroring (that used to be a common
+also discourages [[local copies and mirroring|file collection]] (that used to be a common
practice when [[FTP]] was big).
## Attempts to fix the problems
diff --git a/dependency.mdwn b/dependency.mdwn
@@ -20,14 +20,14 @@ utilize a program or a device, but this documentation can come from several
alternative sources. It can also be omitted if the user has already learned
the necessary information.
-If only one compiler can compile the source code of a program, its compilation dependency is hard. If there's a large variety of different compilers that all succesfully produce a working executable, the dependency is much softer. The same applies to websites and how compatible they are with different browsers. If only a few high-end browsers is supported, the dependency is quite hard.
+If only one compiler can compile the source code of a program, its compilation dependency is hard. If there's a large variety of different compilers that all succesfully produce a working executable, the dependency is much softer. The same applies to websites and how compatible they are with different browsers. If only a few high-end browsers are supported, the dependency is quite hard.
Optional dependencies are soft, especially if they don't change the features or behavior of the program. If it is possible to run an application either natively or in a web browser, the monstrous dependencies of the web browser don't need to be taken in account when assessing the application.
Permacomputing calls for dependency-awareness, both regarding the material
dependencies (the grid, the manufacturing infrastructure, etc.) and the
digital ones. In both cases, the networks of hard dependencies are often
-several orders of magniture larger than they should be, so permacomputing is
+several orders of magnitude larger than they should be, so permacomputing is
concerned about shrinking the networks as well as moving the emphasis
towards soft dependencies.
diff --git a/file_collection.mdwn b/file_collection.mdwn
@@ -31,7 +31,7 @@ underused.
In a permacomputing world, servers that host file collections would be just
as common as public libraries. People would primarily use the servers that
are geographically close to them. They would contain all the commonly used
-software and documentation (along with their complete
-[[dependency|dependencies]]) along with large amounts of other freely
+software and documentation (and their complete
+[[dependencies|dependency]]) along with large amounts of other freely
distributable media (books, entertainment, reference databases such as
Wikipedia, etc.)
