commit 8a208ed256a0642582d9d14292709d238309f369
parent 7b8a90c9b0438eefdc00778d932ed2609605f083
Author: ugrnm <ugrnm@web>
Date: Fri, 6 Jun 2025 11:11:01 +0200
empty web commit
Diffstat:
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/build_on_solid_ground.mdwn b/build_on_solid_ground.mdwn
@@ -8,6 +8,9 @@ What can YOU do
With or without a computer: * Consider using software that runs locally, is open-sourced, and has a thriving user community or is well-documented * Try to pick software that favours slow release cycles and thorough testing over rolling updates. * try to use smaller, more general-purpose tools instead of complex, prescriptive all-in-one solutions * You may also read this as "grow roots to a solid ground". Learn things that last. Learn the history of the technology you use.
-When creating and maintaining software, digital tools or infrastructure * Avoid unreliable dependencies, especially as hard (non-optional) dependencies. If you can't avoid them (in case of software), put them in the same place where you have your program available. * It is possible to support several target platforms. In case of lasting programs, one of these should be a bedrock platform, or instruction set, that does not change too much and therefore increase accessibility, portability and fallback scenarios. * Imagine some of your users will never be able to get an update or find support - think about how they might solve their problems. * Try to use standard file and data exchange formats, ideally formats that are human-readable. * Don't take anything for granted. Especially don't expect the infrastructure such as the power grid and global networking to continue working indefinitely.
+When creating and maintaining software, digital tools or infrastructure
+
+* Avoid unreliable dependencies, especially those hard (non-optional) dependencies. If you can't work around them (in case of software), you can’t avoid using such dependencies, you should bundle them directly with your software keep local copies, instead of relying on downloading them from external servers every time. This way, your software won’t break if those external resources disappear.
+* It is possible to support several target platforms. In case of lasting programs, one of these should be a bedrock platform, or instruction set, that does not change too much and therefore increase accessibility, portability and fallback scenarios. * Imagine some of your users will never be able to get an update or find support - think about how they might solve their problems. * Try to use standard file and data exchange formats, ideally formats that are human-readable. * Don't take anything for granted. Especially don't expect the infrastructure such as the power grid and global networking to continue working indefinitely.
Principle in action: * UXN - https://wiki.xxiivv.com/site/uxn.html * DuskOS - https://duskos.org/ * Actually Portable Executable - https://justine.lol/ape.html * Static HTML Site Generators - https://permacomputing.net/static_site_generator
