permacomputing

permacomputing.net wiki source files
git clone https://git.bleu255.com/repos/permacomputing.git
Log | Files | Refs

commit 856a5eeb44ced718535ad679f0505677c85fdd7f
parent d2bf2a219beabd58d055ca890da1d74cf74c46ee
Author: luen <luen@web>
Date:   Sat Aug 20 13:24:05 +0200

empty web commit
Diffstat:
Principles.mdwn | 2+-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Principles.mdwn b/Principles.mdwn
@@ -27,7 +27,7 @@ Small systems are more likely to have small hardware and energy requirements, as
 * **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.
 * [[Human-scale]]: 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).
-* [[Scalability]] (upwards) is essential only if there is an actual and justifiable need to scale up; down-scalability may often be more elevant.
+* [[Scalability]] (upwards) is essential only if there is an actual and justifiable need to scale up; down-scalability may often be more relevant.
 * **Abundance thinking**. If the computing capacity feels too limited for anything, you can rethink 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!
 
 ## Hope for the best, prepare for the worst