commit 302b483b0bf0ddc8fca77e8d5d9b26a6ae03c76a
parent dd014f9a8204622abc7945bb86a3408fe02dcb94
Author: neau <neau@web>
Date: Sat, 25 Jun 2022 22:42:36 +0200
empty web commit
Diffstat:
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/Principles.mdwn b/Principles.mdwn
@@ -4,11 +4,9 @@ philosophical ones, so feel free to disagree with them or refactor them.
## Care for life
-This is the ethical basis that permacomputing builds on. It refers to the permacultural principles of "care for the earth" and "care for people", but can be well thought of as the basic axiom of all choices.
+This is the ethical basis that permacomputing builds on. It refers to the permacultural principles of "care for the earth" and "care for people", but can be thought of as the basic axiom for all choices.
-In the context of computing, this can be somewhat crudely split into:
-* **Don't do things that harm the biosphere**. Minimize the use of artificial energy, fossil fuels and mined resources. Create low-power systems that use the wide-area network sparingly.
-* **Do things that strengthen the biosphere**. Create systems that either directly or indirectly support this. Use of unsustainable energy can be justified by larger energy savings elsewhere. (Just don't fall into the [[Jevons paradox]] when improving energy efficiency!)
+Minimize the use of artificial energy, fossil fuels and mineral resources. Create low-power systems that use the wide-area network sparingly. Create systems that either directly or indirectly strengthens the biosphere. Don't create system that [[obfuscate waste|Jevons paradox]].
## Care for the chips
@@ -22,9 +20,8 @@ Production of new computing hardware consumes a lot of energy and resources. The
Small systems are more likely to have small hardware and energy requirements, as well as high understandability. They are easier to understand, manage, [[refactor|refactoring]] and [[repurpose]].
-* [[Dependencies|dependency]] (including hardware requirements and whatever external software/libraries the program requires) should also be kept low.
-* Avoid [[pseudosimplicity]] such as user interfaces that hide their operation from the user.
-* Scalability is essential only if there is an actual and justifiable need to scale up.
+[[Dependencies|dependency]] (including hardware requirements and whatever external software/libraries the program requires) should also be kept low. Avoid [[pseudosimplicity]] such as user interfaces that hide their operation from the user.vScalability is essential only if there is an actual and justifiable need to scale up.
+
* **Accumulate wisdom and experience rather than codebase**.
* **Low complexity is beautiful**. This is also relevant to e.g. visual media where "high quality" is often thought to stem from high resolutions and large bitrates.
* **Human-sized computing**: a reasonable level of complexity for a computing system is that it can be entirely understood by a single person (from the low-level hardware details to the application-level quirks).
