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 5101f15b8d895667eff63ce1014eaf0c1695a539
parent 1b39e5ec9ba4941321d6f82f9e46aa2afb6f6c19
Author: neau <neau@web>
Date:   Fri, 24 Jun 2022 01:10:57 +0200

empty web commit

Diffstat:
MAssessments.mdwn | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Assessments.mdwn b/Assessments.mdwn @@ -1,6 +1,6 @@ Permacomputing is also learning to deal with existing technologies, often trying to find the least evil among bad alternatives. In [[hardware]] we can't afford being too picky because we'll want to lengthen the lifespans of already existing even pieces of hardware, but in [[software]] we usually have more choice. -When assessing software and hardware, we'll want to focus on technicalities such as resource use (especially energy use), dependencies and documentation – mostly because many pieces of today's technology fail miserably in these areas. +When assessing software and hardware, we'll want to focus on technicalities such as resource use (especially [[energy use]]), [[dependencies]] and [[documentation]] – mostly because many pieces of today's technology fail miserably in these areas. See also: