commit 69a69f7a15c669cd0f910eb031e1fc1c3531c5a3
parent 301691a6340d332d7b55da6e78ac9b33819a5a32
Author: Ville-Matias Heikkila <viznut@low.fi>
Date: Fri, 15 Dec 2023 17:08:39 +0200
merge properties to permacomputing
Diffstat:
2 files changed, 25 insertions(+), 31 deletions(-)
diff --git a/permacomputing.mdwn b/permacomputing.mdwn
@@ -33,21 +33,33 @@ _a return to the past_. We want to investigate what a permacomputing way of
life could be, and what sort of transformative computational culture and
aesthetics it could bring forward.
-The principles of permacomputing are: care for life, care for the chips,
-keep it small, hope for the best, prepare for the worst, keep it flexible,
-build on solid ground, amplify awareness, expose everything, respond to
-changes, everything has a place.
+The [[principles]] of permacomputing are:
-These principles concretely manifest themselves in various forms so as to
+ * Care for life
+ * Care for the chips
+ * Keep it small
+ * Hope for the best, prepare for the worst
+ * Keep it flexible
+ * Build on solid ground
+ * Amplify awareness
+ * Expose everything
+ * Respond to changes
+ * Everything has a place.
+
+Properties of permacomputing systems
+====================================
+
+The principles concretely manifest themselves in various forms so as to
highlight the following properties:
-* accessible: well documented and adaptable to an individual's needs.
-* compatible: works on a variety of architectures.
-* efficient: uses as little resource (power, memory, etc) as possible,
- minimization
-* flexible: modular, portable, adapts to various use-cases.
-* resilient: repairable, descent-friendly, offline-first and low-maintenance,
- designed for disassembly, planned for longetivity, planned longevity,
- lifespan maximization, designed for descent
+* **accessible**: well documented and adaptable to an individual's needs.
+* **compatible**: works on a variety of architectures.
+* **efficient**: uses as little resources (power, memory, etc) as possible ([[minimization]]).
+* **flexible**: modular, portable, adapts to various use-cases.
+* ****resilient**: repairable, [[design for descent|descent-friendly]], [[offline first|offline-first]], low-maintenance, designed for disassembly, [[planned longevity|planned for longevity]], [[maximized lifespan|lifespan maximization]], [[design for descent|designed for descent]]
+Some additional concerns are of indirect interest because they impose costs on the entire end-to-end process of software creation:
+* it's [[bootstrapped|bootstrapping]] from machine code without circular reasoning (bootstrappable builds)
+* it's obvious what source code went into it (reproducible builds)
+* it's easy to audit its source code, including all dependencies
diff --git a/properties.mdwn b/properties.mdwn
@@ -1,18 +0,0 @@
-More fine-grained properties of permacomputing systems
-======================================================
-
-[[Permacomputing]] is a broad idea that encompasses many concerns. This page is an ongoing attempt to enumerate concerns shared by Permacomputing and/or related [[communities]]. They're all beneficial. Different communities may strive to get to them in different orders.
-
-Human use of computing will be more sustainable if programs and devices are:
-
-* **accessible**: well documented and adaptable to an individual's needs.
-* **compatible**: works on a variety of architectures.
-* **efficient**: uses as little resources(power, memory, etc) as needed.
-* **flexible**: modular, portable, adapts to various use-cases.
-* **resilient**: repairable, descend-friendly, offline-first and low-maintenance.
-
-Some additional concerns are of indirect interest because they impose costs on the entire end-to-end process of software creation. Software will be more minimalist if:
-
-* it's always [[bootstrapped|bootstrapping]] from machine code without circular reasoning (bootstrappable builds)
-* it's obvious what source code went into it (reproducible builds)
-* it's easy to audit its source code, including all dependencies
