User:Rudxain/Permacomputing: Difference between revisions

Line 8:

*'''Stability'''. "If it ain't broke, don't fix it". But I prefer [[wikipedia:G._K._Chesterton#Chesterton's_fence|Chesterton's Fence]].

*'''Sustainability'''. The most important one!

==Why==

Here's a quote from 100R (links added by me; typos corrected):<ref>https://100r.co/site/weathering_software_winter.html</ref><blockquote>Many of the tools that we thought we could rely on broke down, whether it is [[Apple]] products, or software that require [[Subscription service|subscription services]], <abbr>[[Digital rights management|DRM]]</abbr>, etc. As an artist you spend time developing a skill, you become a Photoshop illustrator. When your connection to the internet fails and that the software locks up, that skill that you thought was [[Right to own|yours]] was actually entirely owned by someone, and can be taken away.

Even though we've been paying for this sort of software for years, the moment that you can't have access to [[Forced account|authenticate yourself]] that skill is gone. We didn't expect this, it scared us.</blockquote>Here's one from Maxime Chevalier-Boisvert (links added):<ref>https://github.com/maximecb/uvm/blob/778114c4adf9a928a77c3491bb8dd3c1e464fd84/doc/vision.md</ref><blockquote>We live in a world where software is increasingly complex, and increasingly fragile as a result. It's very easy to end up in a situation where software that was working just fine a few months ago can no longer compile and run due to broken dependencies. One of the main goals of UVM is to combat the phenomenon known as [[wikipedia:Software_rot|"code rot" or "bit rot"]].

[...]

There seems to be a growing interest in [[wikipedia:Retrocomputing|retrocomputing]], and that interest likely stems, in large part, because the complexity of modern computer systems and their software environment is extremely high, and there is constant unnecessary churn, which becomes exhausting. At some point, programmers just want to build, and there is a natural desire to declutter and have fun.</blockquote>Jeff Huang:<ref>{{Cite web |last=Huang |first=Jeff |date=2019-12-19 |title=This Page is Designed to Last: A Manifesto for Preserving Content on the Web |url=https://jeffhuang.com/designed_to_last/ |access-date=2026-04-26}}</ref><blockquote>Bookmark after bookmark led to dead link after dead link. What's vanished: unique pieces of writing on kuro5hin about tech culture; a collection of mathematical puzzles and their associated discussion by academics that my father introduced me to; Woodman's Reverse Engineering tutorials from my high school years, where I first tasted the feeling of control over software; even my most recent bookmark, a series of posts on Google+ exposing usb-c chargers' non-compliance with the specification, all disappeared.

This is more than just [[wikipedia:Link_rot|link rot]], it's the increasing complexity of keeping alive indie content on the web, leading to a reliance on platforms and time-sorted publication formats (blogs, feeds, tweets).</blockquote>

== Suggestions ==

Ideally, this should be a guide, but there is no one-size-fits-all guide to "achieve permacompute nirvana". So here's a list of my own suggestions/"guidelines":

===Programming languages===

Line 27:

Line 41:

*[[wikipedia:Erlang_(programming_language)|Erlang]] and [[wikipedia:Elixir_(programming_language)|Elixir]]

*[[wikipedia:Ada_(programming_language)|Ada]]

~~==Why==~~

Here's a quote from 100R (links added by me; typos corrected):<ref>https://100r.co/site/weathering_software_winter.html</ref><blockquote>Many of the tools that we thought we could rely on broke down, whether it is [[Apple]] products, or software that require [[Subscription service|subscription services]], <abbr>[[Digital rights management|DRM]]</abbr>, etc. As an artist you spend time developing a skill, you become a Photoshop illustrator. When your connection to the internet fails and that the software locks up, that skill that you thought was [[Right to own|yours]] was actually entirely owned by someone, and can be taken away.

Even though we've been paying for this sort of software for years, the moment that you can't have access to [[Forced account|authenticate yourself]] that skill is gone. We didn't expect this, it scared us.</blockquote>Here's one from Maxime Chevalier-Boisvert (links added):<ref>https://github.com/maximecb/uvm/blob/778114c4adf9a928a77c3491bb8dd3c1e464fd84/doc/vision.md</ref><blockquote>We live in a world where software is increasingly complex, and increasingly fragile as a result. It's very easy to end up in a situation where software that was working just fine a few months ago can no longer compile and run due to broken dependencies. One of the main goals of UVM is to combat the phenomenon known as [[wikipedia:Software_rot|"code rot" or "bit rot"]].

~~[...]~~

There seems to be a growing interest in [[wikipedia:Retrocomputing|retrocomputing]], and that interest likely stems, in large part, because the complexity of modern computer systems and their software environment is extremely high, and there is constant unnecessary churn, which becomes exhausting. At some point, programmers just want to build, and there is a natural desire to declutter and have fun.</blockquote>Jeff Huang:<ref>{{Cite web |last=Huang |first=Jeff |date=2019-12-19 |title=This Page is Designed to Last: A Manifesto for Preserving Content on the Web |url=https://jeffhuang.com/designed_to_last/ |access-date=2026-04-26}}</ref><blockquote>Bookmark after bookmark led to dead link after dead link. What's vanished: unique pieces of writing on kuro5hin about tech culture; a collection of mathematical puzzles and their associated discussion by academics that my father introduced me to; Woodman's Reverse Engineering tutorials from my high school years, where I first tasted the feeling of control over software; even my most recent bookmark, a series of posts on Google+ exposing usb-c chargers' non-compliance with the specification, all disappeared.

This is more than just [[wikipedia:Link_rot|link rot]], it's the increasing complexity of keeping alive indie content on the web, leading to a reliance on platforms and time-sorted publication formats (blogs, feeds, tweets).</blockquote>

==External links==

*[https://geminiprotocol.net/docs/faq-section-6.gmi#64-what-is-permacomputing Project Gemini FAQ - §6 Gemini-adjacent technologies and cultures § What is permacomputing?]

*[https://github.com/thisisisa/awesome-permacomputing etc...]

@@ Line 8: / Line 8: @@
 *'''Stability'''. "If it ain't broke, don't fix it". But I prefer [[wikipedia:G._K._Chesterton#Chesterton's_fence|Chesterton's Fence]].
 *'''Sustainability'''. The most important one!
+==Why==
+Here's a quote from 100R (links added by me; typos corrected):<ref>https://100r.co/site/weathering_software_winter.html</ref><blockquote>Many of the tools that we thought we could rely on broke down, whether it is [[Apple]] products, or software that require [[Subscription service|subscription services]], <abbr>[[Digital rights management|DRM]]</abbr>, etc. As an artist you spend time developing a skill, you become a Photoshop illustrator. When your connection to the internet fails and that the software locks up, that skill that you thought was [[Right to own|yours]] was actually entirely owned by someone, and can be taken away.
+Even though we've been paying for this sort of software for years, the moment that you can't have access to [[Forced account|authenticate yourself]] that skill is gone. We didn't expect this, it scared us.</blockquote>Here's one from Maxime Chevalier-Boisvert (links added):<ref>https://github.com/maximecb/uvm/blob/778114c4adf9a928a77c3491bb8dd3c1e464fd84/doc/vision.md</ref><blockquote>We live in a world where software is increasingly complex, and increasingly fragile as a result. It's very easy to end up in a situation where software that was working just fine a few months ago can no longer compile and run due to broken dependencies. One of the main goals of UVM is to combat the phenomenon known as [[wikipedia:Software_rot|"code rot" or "bit rot"]].
+[...]
+There seems to be a growing interest in [[wikipedia:Retrocomputing|retrocomputing]], and that interest likely stems, in large part, because the complexity of modern computer systems and their software environment is extremely high, and there is constant unnecessary churn, which becomes exhausting. At some point, programmers just want to build, and there is a natural desire to declutter and have fun.</blockquote>Jeff Huang:<ref>{{Cite web |last=Huang |first=Jeff |date=2019-12-19 |title=This Page is Designed to Last: A Manifesto for Preserving Content on the Web |url=https://jeffhuang.com/designed_to_last/ |access-date=2026-04-26}}</ref><blockquote>Bookmark after bookmark led to dead link after dead link. What's vanished: unique pieces of writing on kuro5hin about tech culture; a collection of mathematical puzzles and their associated discussion by academics that my father introduced me to; Woodman's Reverse Engineering tutorials from my high school years, where I first tasted the feeling of control over software; even my most recent bookmark, a series of posts on Google+ exposing usb-c chargers' non-compliance with the specification, all disappeared.
+This is more than just [[wikipedia:Link_rot|link rot]], it's the increasing complexity of keeping alive indie content on the web, leading to a reliance on platforms and time-sorted publication formats (blogs, feeds, tweets).</blockquote>
+== Suggestions ==
+Ideally, this should be a guide, but there is no one-size-fits-all guide to "achieve permacompute nirvana". So here's a list of my own suggestions/"guidelines":
 ===Programming languages===
@@ Line 27: / Line 41: @@
 *[[wikipedia:Erlang_(programming_language)|Erlang]] and [[wikipedia:Elixir_(programming_language)|Elixir]]
 *[[wikipedia:Ada_(programming_language)|Ada]]
-==Why==
-Here's a quote from 100R (links added by me; typos corrected):<ref>https://100r.co/site/weathering_software_winter.html</ref><blockquote>Many of the tools that we thought we could rely on broke down, whether it is [[Apple]] products, or software that require [[Subscription service|subscription services]], <abbr>[[Digital rights management|DRM]]</abbr>, etc. As an artist you spend time developing a skill, you become a Photoshop illustrator. When your connection to the internet fails and that the software locks up, that skill that you thought was [[Right to own|yours]] was actually entirely owned by someone, and can be taken away.
-Even though we've been paying for this sort of software for years, the moment that you can't have access to [[Forced account|authenticate yourself]] that skill is gone. We didn't expect this, it scared us.</blockquote>Here's one from Maxime Chevalier-Boisvert (links added):<ref>https://github.com/maximecb/uvm/blob/778114c4adf9a928a77c3491bb8dd3c1e464fd84/doc/vision.md</ref><blockquote>We live in a world where software is increasingly complex, and increasingly fragile as a result. It's very easy to end up in a situation where software that was working just fine a few months ago can no longer compile and run due to broken dependencies. One of the main goals of UVM is to combat the phenomenon known as [[wikipedia:Software_rot|"code rot" or "bit rot"]].
-[...]
-There seems to be a growing interest in [[wikipedia:Retrocomputing|retrocomputing]], and that interest likely stems, in large part, because the complexity of modern computer systems and their software environment is extremely high, and there is constant unnecessary churn, which becomes exhausting. At some point, programmers just want to build, and there is a natural desire to declutter and have fun.</blockquote>Jeff Huang:<ref>{{Cite web |last=Huang |first=Jeff |date=2019-12-19 |title=This Page is Designed to Last: A Manifesto for Preserving Content on the Web |url=https://jeffhuang.com/designed_to_last/ |access-date=2026-04-26}}</ref><blockquote>Bookmark after bookmark led to dead link after dead link. What's vanished: unique pieces of writing on kuro5hin about tech culture; a collection of mathematical puzzles and their associated discussion by academics that my father introduced me to; Woodman's Reverse Engineering tutorials from my high school years, where I first tasted the feeling of control over software; even my most recent bookmark, a series of posts on Google+ exposing usb-c chargers' non-compliance with the specification, all disappeared.
-This is more than just [[wikipedia:Link_rot|link rot]], it's the increasing complexity of keeping alive indie content on the web, leading to a reliance on platforms and time-sorted publication formats (blogs, feeds, tweets).</blockquote>
 ==External links==
 *[https://geminiprotocol.net/docs/faq-section-6.gmi#64-what-is-permacomputing Project Gemini FAQ - §6 Gemini-adjacent technologies and cultures § What is permacomputing?]
 *[https://github.com/thisisisa/awesome-permacomputing etc...]