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 24fae06fda62e512e6274051b808a32f5429b955
parent 350f17bebb6f873893536e4430d47943a8375e68
Author: viznut_web <viznut_web@web>
Date:   Sun, 26 Jun 2022 19:14:02 +0200

typos & link

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

diff --git a/Principles.mdwn b/Principles.mdwn @@ -10,7 +10,7 @@ Create low-power systems that strengthens the biosphere and use the wide-area ne ## Care for the chips -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]]. +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|IC]], because of their low material [[recyclability]]. * Respect the quirks and peculiarities of what already exists and [[repair]] what can be repaired. * Create new devices from [[salvaged components|salvage computing]]. @@ -22,7 +22,7 @@ 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.vScalability 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. Scalability 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.