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 1a19b8c6e31d33e29ca55a59fa99a7bc9303531a
parent 76d3c975ee4ef146cf7d3c68ea40655629d7557b
Author: neau <neau@web>
Date:   Wed, 22 Jun 2022 18:25:44 +0200

empty web commit

Diffstat:
MPrinciples.mdwn | 4+++-
1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/Principles.mdwn b/Principles.mdwn @@ -13,7 +13,8 @@ philosophical ones, so feel free to disagree with them or refactor them. * Production of new computing hardware consumes a lot of energy and resources. Therefore, we need to **[[maximize the lifespans|lifespan maximization]]** of hardware components – especially microchips, because of their low material recyclability. Repair what can be repaired, create new devices from old components. * **Accept what already exists**. Appreciate even bad hardware (but also notice its energy consumption). Respect the quirks and peculiarities of each chip and design (this is particularly relevant for [[art]]). Support **[[time-sharing]]** in your local community in order to avoid buying new stuff. -* Push the industry towards **[[Planned longevity]]** and **[[Design for disassembly]]**. +* Push the industry towards **[[Planned longevity]]**. +* [[Design for disassembly]]. ## Keep it small and simple @@ -25,6 +26,7 @@ philosophical ones, so feel free to disagree with them or refactor them. * **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). * **Abundance thinking**. If the computing capacity feels too limited for anything, you can rethink it it from the point of view of abundance (e.g. by taking yourself fifty years back in time): tens of kilobytes of memory, thousands of operations per second – think about all the possibilities! +* [[Design for descent]]. ## Keep it flexible