commit 02a5ee18a4cc222e6ab68bea1bac7bbd95e9c6af parent c5563da08e6104b5580dfc7b10a4401af671aafa Author: Nick Moffitt <nick@zork.net> Date: Wed, 20 May 2026 13:52:42 +0100 link to our UXN page Diffstat:
| M | spacehobo/antipatterns.mdwn | | | 2 | +- |
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/spacehobo/antipatterns.mdwn b/spacehobo/antipatterns.mdwn @@ -17,7 +17,7 @@ One of the reasons that people have trouble understanding definitions is that we ## Permacomputing is not Prescriptive -One resource that shows up prominently in search results is the [Hundred Rabbits talks on Permacomputing](https://100r.co/site/permacomputing_101.html) by Devine Lu Linvega. Their practice involves low-power disconnected living on a sailboat in the Pacific Ocean, and they have developed tools such as [UXN](https://100r.co/site/uxn.html) in service of this. A lot of the writing about Permacomputing comes from their lived experience and that of their shared communities of practice online. +One resource that shows up prominently in search results is the [Hundred Rabbits talks on Permacomputing](https://100r.co/site/permacomputing_101.html) by Devine Lu Linvega. Their practice involves low-power disconnected living on a sailboat in the Pacific Ocean, and they have developed tools such as [[Uxn]] in service of this. A lot of the writing about Permacomputing comes from their lived experience and that of their shared communities of practice online. It would be easy to read through these materials, then, and think "Is Permacomputing necessarily built on stack-based concatenative assembly languages? Is this only about Forth?"