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 9a2871f0cb0993008f2033a927f59d8cc9139680
parent ed9ae093c48003d16f7016fa7012db5fa472c008
Author: neau <neau@web>
Date:   Sat, 25 Jun 2022 04:12:40 +0200

empty web commit

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

diff --git a/properties.mdwn b/properties.mdwn @@ -5,11 +5,11 @@ More fine-grained properties of permacomputing systems Human use of computing will be more sustainable if: -* software can run on any hardware architecture (portability) -* software can run on old hardware (salvage, collapse, right to repair) -* software is energy efficient -* software can be used for a long time (archival, low maintenance) -* software is easy to tailor in the field +* **accessibility**: software is well documented and through a variety of interfaces. +* **compatibility**: software runs a variety of architectures. +* **efficiency**: software uses as little resources(power, memory, etc) as needed. +* **flexibility**: software is modular, portable, adapts to various use-cases. +* **resilient**: software is 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: