permacomputing

Source repository for the main permacomputing wiki site
git clone http://git.permacomputing.net/repos/permacomputing.git # read-only access
Log | Files | Refs

commit 3841e7756694fc585df2b3d1aecd47b9809d7bf9
parent ab12370f22d952944394cd8bb7c4e77c6f4ded96
Author: aw <aw@web>
Date:   Sun, 26 Jun 2022 10:12:33 +0200

empty web commit

Diffstat:
Mproperties.mdwn | 8++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/properties.mdwn b/properties.mdwn @@ -5,14 +5,14 @@ More fine-grained properties of permacomputing systems Human use of computing will be more sustainable if programs and devices are: -* **accessible**: is well documented and adaptable to an individual's needs. +* **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**: is modular, portable, adapts to various use-cases. -* **resilient**: is repairable, descend-friendly, offline-first and low-maintenance. +* **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 from machine code without circular reasoning (bootstrappable builds) +* 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