permacomputing

commit a9a3f358b0082bc976d9c250e1a46fd41d34b1f4
parent b255a4302e54be3906d11bc3a590ce9d651cb6fe
Author: neau <neau@web>
Date:   Wed, 22 Jun 2022 01:19:49 +0200

empty web commit

Diffstat:
M
Assessments.mdwn
 | 
2
+-

1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Assessments.mdwn b/Assessments.mdwn
@@ -1,4 +1,4 @@
-Permacomputing is not just about building an utopia from scratch but dealing 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 even bad pieces of hardware, but in [[software]] we usually have much more choice.
+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.