commit edb3a7f76728a1663a306be69cbec95586404c69
parent c8383d44bbb39cad1c39f3803c4673ef7597dc28
Author: Ville-Matias Heikkila <viznut@low.fi>
Date: Fri, 17 Jun 2022 11:19:15 +0300
Merge branch 'master' of bleu255.com:/var/www/git.bleu255.com/repos/permacomputing
Diffstat:
2 files changed, 5 insertions(+), 9 deletions(-)
diff --git a/Collapse_OS.mdwn b/Collapse_OS.mdwn
@@ -7,6 +7,8 @@
* Read and write from a wide range of storage devices.
* Assemble itself and deploy to another machine.
+**[Dusk OS](https://git.sr.ht/~vdupras/duskos)** will be a similar OS geared at more powerful devices and aimed at general-purpose post-collapse uses.
+
See also:
* [The official website of Collapse OS](http://collapseos.org/)
diff --git a/information_battery.mdwn b/information_battery.mdwn
@@ -1,20 +1,14 @@
Information battery
===================
-An **information battery** refers to the "storage" of surplus energy in the
-form of information (such as computational results) that can be used later
-to lessen the need for computation.
+An **information battery** refers to the "storage" of surplus energy in the form of information (such as intermediate results of computation) that can be used later to lessen the need for computation.
-The concept was introduced in the context of [[supercomputing]], but it has
+The concept was introduced in the context of [supercomputing]], but it has
also been discussed in the context of [[degrowth computing]] in 2022. It
mirrors the permacomputing idea of using surplus energy for slow,
computing-intensive tasks.
-The concept emphasizes the storage of information on a rather short-term
-basis. An example of a more long-term use of surplus energy would be the
-gradual optimization of software: when initially compiling a program, the
-compiler would only do rather lightweight optimizations, and the heavier and
-more computing-intensive ones would be postponed to times of abundance.
+The concept emphasizes the storage of rather temporary information on a rather short-term basis. An example of a more long-term use of surplus energy for more permanent results would be the gradual optimization of software: when initially compiling a program, the compiler would only do rather lightweight optimizations, and the heavier and more computing-intensive ones would be postponed to times of abundance.
See also:
