commit a1dc9265139e44814f8fa75aeeed6cb0feb9050a
parent b982db9d44c024dde0f4a30d5116d4faffd1ac53
Author: Nick Moffitt <nick@zork.net>
Date: Wed, 20 May 2026 15:37:39 +0100
link projects earlier
Diffstat:
1 file changed, 1 insertion(+), 5 deletions(-)
diff --git a/spacehobo/antipatterns.mdwn b/spacehobo/antipatterns.mdwn
@@ -23,11 +23,7 @@ It would be easy to read through these materials, then, and think "Is Permacompu
It is most certainly *not* limited to Forth! It's true that Forth has become something of a meme in permacomputing circles, and newcomers may not understand how much of this is tongue-in-cheek.
-To illustrate this principle, here are some living projects that prove this.
-
-### These things *can be* Permacomputing:
-
-Take a look at the [[projects]] page to see a list of projects that we feel capture the spirit of Permacomputing. They range from 8-bit BASIC and Forth computers to 32-bit Lua programming tools and low-pixel-count photography festivals. They include Linux distributions you can install on old phones or tablets, power monitoring for your existing devices, and ways to distribute site hosting on solar-powered nodes so your traffic "follows the sun".
+To illustrate this principle, here are some living [[projects]] that prove this. These things, and others similar to them, *can be* Permacomputing. They range from 8-bit BASIC and Forth computers to 32-bit Lua programming tools and low-pixel-count photography festivals. They include Linux distributions you can install on old phones or tablets, power monitoring for your existing devices, and ways to distribute site hosting on solar-powered nodes so your traffic "follows the sun".
I say "can be" because it's always possible for a project with noble aims and incredible promise to change. Goals shift, and sometimes people make tradeoffs that ultimately thwart the original aims. Permacomputing is about those goals, and that is why our descriptions of methods and approaches are so fuzzy.
