User:Rudxain/Permacomputing - Revision history

Rudxain: Why->Motivation

2026-04-29T01:12:46Z

Why->Motivation

← Older revision		Revision as of 01:12, 29 April 2026
Line 3:		Line 3:
	Permacomputing is the antithesis of [[planned obsolescence]] (and anything related to it) and [[Bloatware\|bloat]].		Permacomputing is the antithesis of [[planned obsolescence]] (and anything related to it) and [[Bloatware\|bloat]].

	==~~Why~~==		==Motivation==
	Here's a quote from [[wikipedia:Hundred_Rabbits#Permacomputing\|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.		Here's a quote from [[wikipedia:Hundred_Rabbits#Permacomputing\|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.

Rudxain: how could I forget Lua the GOAT?

2026-04-28T23:53:17Z

how could I forget Lua the GOAT?

← Older revision		Revision as of 23:53, 28 April 2026
Line 26:		Line 26:
	Examples of simple programming-languages (typically [[wikipedia:Turing_tarpit\|Turing tarpits]]):		Examples of simple programming-languages (typically [[wikipedia:Turing_tarpit\|Turing tarpits]]):

	* [[wikipedia:Forth_(programming_language)\|Forth]].<ref>https://github.com/cesarblum/sectorforth</ref> Recommended by 100R.		*[[wikipedia:Forth_(programming_language)\|Forth]].<ref>https://github.com/cesarblum/sectorforth</ref> Recommended by 100R.
	* [[wikipedia:Lisp_(programming_language)\|Lisp]]<ref>{{Cite web \|last=Tunney \|first=Justine \|date=2021-10-30 \|title=SectorLISP Now Fits in One Sector \|url=https://justine.lol/sectorlisp/ \|access-date=2026-04-26}}</ref>		*[[wikipedia:Lisp_(programming_language)\|Lisp]]<ref>{{Cite web \|last=Tunney \|first=Justine \|date=2021-10-30 \|title=SectorLISP Now Fits in One Sector \|url=https://justine.lol/sectorlisp/ \|access-date=2026-04-26}}</ref>
	*[[wikipedia:Lambda_calculus\|λ-Calculus]].<ref>{{Cite web \|last=Tunney \|first=Justine \|date=2022-02-27 \|title=Lambda Calculus in 383 Bytes \|url=https://justine.lol/lambda/ \|access-date=2026-04-26}}</ref> IMO, the most minimal of all. No way to beat it!		*[[wikipedia:Lambda_calculus\|λ-Calculus]].<ref>{{Cite web \|last=Tunney \|first=Justine \|date=2022-02-27 \|title=Lambda Calculus in 383 Bytes \|url=https://justine.lol/lambda/ \|access-date=2026-04-26}}</ref> IMO, the most minimal of all. No way to beat it!
	*[[wikipedia:Brainfuck\|Brainfuck]]		*[[wikipedia:Brainfuck\|Brainfuck]]
Line 36:		Line 36:
	Examples:		Examples:

	* [[User:Rudxain/Unix\|Unix-like systems]], and their [https://pubs.opengroup.org/onlinepubs/9799919799/idx/utilities.html utilities]		*[[User:Rudxain/Unix\|Unix-like systems]], and their [https://pubs.opengroup.org/onlinepubs/9799919799/idx/utilities.html utilities]
	* [[wikipedia:MS-DOS\|MS-DOS]], because it's the common subset among [[Microsoft Windows\|Windows]] systems		*[[wikipedia:MS-DOS\|MS-DOS]], because it's the common subset among [[Microsoft Windows\|Windows]] systems
	* [[wikipedia:C_(programming_language)\|C]]. BTW, there's a C-compiler that makes ''extremely''-portable executables.<ref>https://justine.lol/cosmopolitan/</ref>		*[[wikipedia:C_(programming_language)\|C]]. BTW, there's a C-compiler that makes ''extremely''-portable executables.<ref>https://justine.lol/cosmopolitan/</ref>

	===Interoperability===		===Interoperability===
Line 46:		Line 46:
	Examples:		Examples:

	* [[wikipedia:Zig_(programming_language)\|Zig]], which has "reusable software" as part of its slogan. It also has C [[wikipedia:Interoperability\|interop]]. However, it's still in an [[wikipedia:API#Public_API_implications\|API-unstable]] state, so you'll have to wait before everything is settled.		*[[wikipedia:Lua\|Lua]]. A simple and powerful lang built for embeddability and [[wikipedia:Extensibility\|extensibility]]. It's also '''the''' lang used to make MediaWiki modules.
			*[[wikipedia:Zig_(programming_language)\|Zig]], which has "reusable software" as part of its slogan. It also has C [[wikipedia:Interoperability\|interop]]. However, it's still in an [[wikipedia:API#Public_API_implications\|API-unstable]] state, so you'll have to wait before everything is settled.

	===Archivability===		===Archivability===

Rudxain: I'm not qualified to give suggestions, so I'll just use them as examples in the Guidelines section

2026-04-27T23:25:49Z

I'm not qualified to give suggestions, so I'll just use them as examples in the Guidelines section

@@ Line 23: / Line 23: @@
 This principle is the basis of [[wikipedia:Bootstrapping_(compilers)|bootstrapping]]. Simple (and tedious) tools can be used to make useful (and complex) tools! This goes hand-in-hand with [[wikipedia:Reproducible_builds|reproducible builds]], which [[User:Rudxain/Object transparency movement|improves transparency]].<ref>https://bootstrappable.org/</ref>
 ===Ubiquity===
 If the tool is hard to recreate, ensure it's mostly [[wikipedia:Omnipresence|omnipresent]]. This is "[[wikipedia:Redundancy_(engineering)|useful redundancy]]", as I call it. This way, you can typically rely on it being available in almost any situation.
 ===Interoperability===
 {{Main|wikipedia:Interoperability}}
 Ensure the tool-set/tool-chain you use is like an orchestra: there must be some ''harmony''. That is, ensure many tools can communicate with each other using common formats and protocols. Ensure ''those'' formats and protocols follow the same guidelines as the tools (simple, [[wikipedia:Open_standard|open]], ubiquitous, etc...). In short, follow [[wikipedia:Unix_philosophy|the Unix Philosophy]]. Even a tiny set of simple tools can be orders-of-magnitude more useful than a single simple tool.
 ===Archivability===
@@ Line 37: / Line 54: @@
 BTW, there's a common misconception that physical media is better than digital media. The main problem is [[wikipedia:Centralized_computing|centralized]] media (typically on the [[Cloud (service)|cloud]]). Physical media is ''still'' digital (unless it's analog, like magnetic tape or vinyl records), it's just outside of a device.
 ==External links==
@@ Line 76: / Line 66: @@
 *[[wikipedia:KISS_principle|K.I.S.S. principle]]
 *[[wikipedia:Minimalism_(computing)|Minimalism in computing]]
 ==References==
 {{reflist}}

Rudxain: data-hoard is optional

2026-04-27T22:43:53Z

data-hoard is optional

← Older revision		Revision as of 22:43, 27 April 2026
Line 34:		Line 34:
	(yes, that's a [[wikt:archivability\|real word]]) this is more about data/info than computing. When all else fails, at the very least, ensure data can be easily copied and archived. This isn't just for tools, it's about any kind of data: personal memories, historical events, etc...		(yes, that's a [[wikt:archivability\|real word]]) this is more about data/info than computing. When all else fails, at the very least, ensure data can be easily copied and archived. This isn't just for tools, it's about any kind of data: personal memories, historical events, etc...

	Universal truths, such as those found in math and physics, can be "extracted" and derived any time. But ''events'' are more unique, so those are in great danger of being forgotten (see also: [[wikipedia:Lost_media\|lost media]]).		Universal truths, such as those found in math and physics, can be "extracted" and derived any time. But ''events'' are more unique, so those are in great danger of being forgotten (see also: [[wikipedia:Lost_media\|lost media]]). You don't have to become a [[wikipedia:Digital_hoarding\|data hoarder]], just focus on important data.

	BTW, there's a common misconception that physical media is better than digital media. The main problem is [[wikipedia:Centralized_computing\|centralized]] media (typically on the [[Cloud (service)\|cloud]]). Physical media is ''still'' digital (unless it's analog, like magnetic tape or vinyl records), it's just outside of a device.		BTW, there's a common misconception that physical media is better than digital media. The main problem is [[wikipedia:Centralized_computing\|centralized]] media (typically on the [[Cloud (service)\|cloud]]). Physical media is ''still'' digital (unless it's analog, like magnetic tape or vinyl records), it's just outside of a device.

Rudxain: problem is central, not cloud

2026-04-27T22:41:40Z

problem is central, not cloud

← Older revision		Revision as of 22:41, 27 April 2026
Line 36:		Line 36:
	Universal truths, such as those found in math and physics, can be "extracted" and derived any time. But ''events'' are more unique, so those are in great danger of being forgotten (see also: [[wikipedia:Lost_media\|lost media]]).		Universal truths, such as those found in math and physics, can be "extracted" and derived any time. But ''events'' are more unique, so those are in great danger of being forgotten (see also: [[wikipedia:Lost_media\|lost media]]).

	BTW, there's a common misconception that physical media is better than digital media. The ~~real~~ problem is [[~~Cloud (service)~~\|~~cloud~~]] media: the ~~owners of the server hosting the media can delete it or~~ [[~~Pay-walling~~\|~~paywall~~]] ~~it anytime they want~~. Physical media is ''still'' digital (unless it's analog, like magnetic tape or vinyl records), it's just outside of a device.		BTW, there's a common misconception that physical media is better than digital media. The main problem is [[wikipedia:Centralized_computing\|centralized]] media (typically on the [[Cloud (service)\|cloud]]). Physical media is ''still'' digital (unless it's analog, like magnetic tape or vinyl records), it's just outside of a device.

	==Suggestions==		==Suggestions==

Rudxain: better and concise intro. move stuff to "See also"

2026-04-27T22:27:35Z

better and concise intro. move stuff to "See also"

← Older revision		Revision as of 22:27, 27 April 2026
Line 1:		Line 1:
	'''Permacomputing''' is a concept and [https://permacomputing.net/ movement] which consists ~~on extending the longevity~~ of information technology (IT) devices and [[wikipedia:Data_preservation\|data preservation]].		'''Permacomputing''' is a concept and [https://permacomputing.net/ movement] which consists of [[wikipedia:Sustainability\|sustainable]] information technology (IT) devices and [[wikipedia:Data_preservation\|data preservation]]. In short, [[wikipedia:Permaculture\|'''permaculture''']] in computing.

	Permacomputing is the antithesis of [[planned obsolescence]] (and anything related to it) and [[Bloatware\|bloat]].		Permacomputing is the antithesis of [[planned obsolescence]] (and anything related to it) and [[Bloatware\|bloat]].

	~~Permacomputing focuses on:~~

	*'''Simplicity''' (see [[wikipedia:KISS_principle\|KISS]]) and [[wikipedia:Minimalism_(computing)\|minimalism]]. Because "[https://grugbrain.dev/ complexity bad]". Though, this is not a core value, it's actually a means to an end.
	*'''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==		==Why==
Line 77:		Line 71:
	==See also==		==See also==

			*[[wikipedia:Appropriate_technology\|Appropriate technology]]
	*[[Projects:Archive everything\|Archive everything]]		*[[Projects:Archive everything\|Archive everything]]
	*[[Self-hosting]]		*[[Self-hosting]]
			*[[wikipedia:KISS_principle\|K.I.S.S. principle]]
			*[[wikipedia:Minimalism_(computing)\|Minimalism in computing]]

	==References==		==References==
	{{reflist}}		{{reflist}}

Rudxain: physical media misconception

2026-04-27T07:45:31Z

physical media misconception

← Older revision		Revision as of 07:45, 27 April 2026
Line 37:		Line 37:
	Ensure the tool-set/tool-chain you use is like an orchestra: there must be some ''harmony''. That is, ensure many tools can communicate with each other using common formats and protocols. Ensure ''those'' formats and protocols follow the same guidelines as the tools (simple, [[wikipedia:Open_standard\|open]], ubiquitous, etc...). In short, follow [[wikipedia:Unix_philosophy\|the Unix Philosophy]]. Even a tiny set of simple tools can be orders-of-magnitude more useful than a single simple tool.		Ensure the tool-set/tool-chain you use is like an orchestra: there must be some ''harmony''. That is, ensure many tools can communicate with each other using common formats and protocols. Ensure ''those'' formats and protocols follow the same guidelines as the tools (simple, [[wikipedia:Open_standard\|open]], ubiquitous, etc...). In short, follow [[wikipedia:Unix_philosophy\|the Unix Philosophy]]. Even a tiny set of simple tools can be orders-of-magnitude more useful than a single simple tool.

	=== Archivability ===		===Archivability===
	(yes, that's a [[wikt:archivability\|real word]]) this is more about data/info than computing. When all else fails, at the very least, ensure data can be easily copied and archived. This isn't just for tools, it's about any kind of data: personal memories, historical events, etc...		(yes, that's a [[wikt:archivability\|real word]]) this is more about data/info than computing. When all else fails, at the very least, ensure data can be easily copied and archived. This isn't just for tools, it's about any kind of data: personal memories, historical events, etc...

	Universal truths, such as those found in math and physics, can be "extracted" and derived any time. But ''events'' are more unique, so those are in great danger of being forgotten.		Universal truths, such as those found in math and physics, can be "extracted" and derived any time. But ''events'' are more unique, so those are in great danger of being forgotten (see also: [[wikipedia:Lost_media\|lost media]]).

	~~See also~~: [[~~wikipedia:Lost_media~~\|~~lost media~~]].		BTW, there's a common misconception that physical media is better than digital media. The real problem is [[Cloud (service)\|cloud]] media: the owners of the server hosting the media can delete it or [[Pay-walling\|paywall]] it anytime they want. Physical media is ''still'' digital (unless it's analog, like magnetic tape or vinyl records), it's just outside of a device.

	==Suggestions==		==Suggestions==

Rudxain: Archivability

2026-04-27T07:37:07Z

Archivability

← Older revision		Revision as of 07:37, 27 April 2026
Line 36:		Line 36:
	{{Main\|wikipedia:Interoperability}}		{{Main\|wikipedia:Interoperability}}
	Ensure the tool-set/tool-chain you use is like an orchestra: there must be some ''harmony''. That is, ensure many tools can communicate with each other using common formats and protocols. Ensure ''those'' formats and protocols follow the same guidelines as the tools (simple, [[wikipedia:Open_standard\|open]], ubiquitous, etc...). In short, follow [[wikipedia:Unix_philosophy\|the Unix Philosophy]]. Even a tiny set of simple tools can be orders-of-magnitude more useful than a single simple tool.		Ensure the tool-set/tool-chain you use is like an orchestra: there must be some ''harmony''. That is, ensure many tools can communicate with each other using common formats and protocols. Ensure ''those'' formats and protocols follow the same guidelines as the tools (simple, [[wikipedia:Open_standard\|open]], ubiquitous, etc...). In short, follow [[wikipedia:Unix_philosophy\|the Unix Philosophy]]. Even a tiny set of simple tools can be orders-of-magnitude more useful than a single simple tool.

			=== Archivability ===
			(yes, that's a [[wikt:archivability\|real word]]) this is more about data/info than computing. When all else fails, at the very least, ensure data can be easily copied and archived. This isn't just for tools, it's about any kind of data: personal memories, historical events, etc...

			Universal truths, such as those found in math and physics, can be "extracted" and derived any time. But ''events'' are more unique, so those are in great danger of being forgotten.

			See also: [[wikipedia:Lost_media\|lost media]].

	==Suggestions==		==Suggestions==
Line 59:		Line 66:
	*[[wikipedia:Ada_(programming_language)\|Ada]]		*[[wikipedia:Ada_(programming_language)\|Ada]]

	=== Systems ===		===Systems===
	If you have them available, choose Unix-like systems and/or [[wikipedia:MS-DOS\|MS-DOS]]. Avoid [[Microsoft Windows\|Windows]] and [[Apple macOS\|Mac]]!		If you have them available, choose Unix-like systems and/or [[wikipedia:MS-DOS\|MS-DOS]]. Avoid [[Microsoft Windows\|Windows]] and [[Apple macOS\|Mac]]!

Rudxain: suggest systems

2026-04-27T07:16:14Z

suggest systems

← Older revision		Revision as of 07:16, 27 April 2026
Line 20:		Line 20:
	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>		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>

	== Guidelines ==		==Guidelines==
	This is not a [[Portal:User Guides\|guide]], this is a set of "universal" principles.		This is not a [[Portal:User Guides\|guide]], this is a set of "universal" principles.

	=== Ease of re-creation ===		===Ease of re-creation===
	Simple tools are easy to re-implement from scratch, so choose (and learn) simple tools whenever possible. If you ever find yourself in a situation where you have a computer with no software, or you don't even have a computer, you can rely on simple tools and skills to make what you need (or find someone else to do it).		Simple tools are easy to re-implement from scratch, so choose (and learn) simple tools whenever possible. If you ever find yourself in a situation where you have a computer with no software, or you don't even have a computer, you can rely on simple tools and skills to make what you need (or find someone else to do it).

Line 30:		Line 30:
	This principle is the basis of [[wikipedia:Bootstrapping_(compilers)\|bootstrapping]]. Simple (and tedious) tools can be used to make useful (and complex) tools! This goes hand-in-hand with [[wikipedia:Reproducible_builds\|reproducible builds]], which [[User:Rudxain/Object transparency movement\|improves transparency]].<ref>https://bootstrappable.org/</ref>		This principle is the basis of [[wikipedia:Bootstrapping_(compilers)\|bootstrapping]]. Simple (and tedious) tools can be used to make useful (and complex) tools! This goes hand-in-hand with [[wikipedia:Reproducible_builds\|reproducible builds]], which [[User:Rudxain/Object transparency movement\|improves transparency]].<ref>https://bootstrappable.org/</ref>

	=== Ubiquity ===		===Ubiquity===
	If the tool is hard to recreate, ensure it's mostly [[wikipedia:Omnipresence\|omnipresent]]. This is "[[wikipedia:Redundancy_(engineering)\|useful redundancy]]", as I call it. This way, you can typically rely on it being available in almost any situation.		If the tool is hard to recreate, ensure it's mostly [[wikipedia:Omnipresence\|omnipresent]]. This is "[[wikipedia:Redundancy_(engineering)\|useful redundancy]]", as I call it. This way, you can typically rely on it being available in almost any situation.

	=== Interoperability ===		===Interoperability===
	{{Main\|wikipedia:Interoperability}}		{{Main\|wikipedia:Interoperability}}
	Ensure the tool-set/tool-chain you use is like an orchestra: there must be some ''harmony''. That is, ensure many tools can communicate with each other using common formats and protocols. Ensure ''those'' formats and protocols follow the same guidelines as the tools (simple, [[wikipedia:Open_standard\|open]], ubiquitous, etc...). In short, follow [[wikipedia:Unix_philosophy\|the Unix Philosophy]]. Even a tiny set of simple tools can be orders-of-magnitude more useful than a single simple tool.		Ensure the tool-set/tool-chain you use is like an orchestra: there must be some ''harmony''. That is, ensure many tools can communicate with each other using common formats and protocols. Ensure ''those'' formats and protocols follow the same guidelines as the tools (simple, [[wikipedia:Open_standard\|open]], ubiquitous, etc...). In short, follow [[wikipedia:Unix_philosophy\|the Unix Philosophy]]. Even a tiny set of simple tools can be orders-of-magnitude more useful than a single simple tool.
Line 58:		Line 58:
	*[[wikipedia:Erlang_(programming_language)\|Erlang]] and [[wikipedia:Elixir_(programming_language)\|Elixir]]		*[[wikipedia:Erlang_(programming_language)\|Erlang]] and [[wikipedia:Elixir_(programming_language)\|Elixir]]
	*[[wikipedia:Ada_(programming_language)\|Ada]]		*[[wikipedia:Ada_(programming_language)\|Ada]]

			=== Systems ===
			If you have them available, choose Unix-like systems and/or [[wikipedia:MS-DOS\|MS-DOS]]. Avoid [[Microsoft Windows\|Windows]] and [[Apple macOS\|Mac]]!

			If you don't have [[wikipedia:Operating_system\|OSes]] available, you'll have to make one from scratch. While this seems hard (and it is), it's actually ''much'' easier when you focus on basic features of an OS, and avoid all the "nice" features and complex optimizations. There was a time when [[wikipedia:Boot_disk\|bootable programs]] where the norm, and each program needed a basic "kernel" to manage resources.<ref>{{Cite web \|last=Muratori \|first=Casey \|date=2018-05-12 \|title=The Thirty Million Line Problem \|url=https://youtu.be/kZRE7HIO3vk \|url-status=live \|access-date=2026-03-15 \|website=Molly Rocket \|via=YouTube}}</ref>

	==External links==		==External links==

Rudxain: add core guidelines/principles

2026-04-27T06:39:44Z

add core guidelines/principles

@@ Line 19: / Line 19: @@
 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":
+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 concrete suggestions and examples:
 ===Programming languages===

← Older revision		Revision as of 23:53, 28 April 2026
Line 26:		Line 26:
	Examples of simple programming-languages (typically [[wikipedia:Turing_tarpit\|Turing tarpits]]):		Examples of simple programming-languages (typically [[wikipedia:Turing_tarpit\|Turing tarpits]]):

	* [[wikipedia:Forth_(programming_language)\|Forth]].<ref>https://github.com/cesarblum/sectorforth</ref> Recommended by 100R.		*[[wikipedia:Forth_(programming_language)\|Forth]].<ref>https://github.com/cesarblum/sectorforth</ref> Recommended by 100R.
	* [[wikipedia:Lisp_(programming_language)\|Lisp]]<ref>{{Cite web \|last=Tunney \|first=Justine \|date=2021-10-30 \|title=SectorLISP Now Fits in One Sector \|url=https://justine.lol/sectorlisp/ \|access-date=2026-04-26}}</ref>		*[[wikipedia:Lisp_(programming_language)\|Lisp]]<ref>{{Cite web \|last=Tunney \|first=Justine \|date=2021-10-30 \|title=SectorLISP Now Fits in One Sector \|url=https://justine.lol/sectorlisp/ \|access-date=2026-04-26}}</ref>
	*[[wikipedia:Lambda_calculus\|λ-Calculus]].<ref>{{Cite web \|last=Tunney \|first=Justine \|date=2022-02-27 \|title=Lambda Calculus in 383 Bytes \|url=https://justine.lol/lambda/ \|access-date=2026-04-26}}</ref> IMO, the most minimal of all. No way to beat it!		*[[wikipedia:Lambda_calculus\|λ-Calculus]].<ref>{{Cite web \|last=Tunney \|first=Justine \|date=2022-02-27 \|title=Lambda Calculus in 383 Bytes \|url=https://justine.lol/lambda/ \|access-date=2026-04-26}}</ref> IMO, the most minimal of all. No way to beat it!
	*[[wikipedia:Brainfuck\|Brainfuck]]		*[[wikipedia:Brainfuck\|Brainfuck]]
Line 36:		Line 36:
	Examples:		Examples:

	* [[User:Rudxain/Unix\|Unix-like systems]], and their [https://pubs.opengroup.org/onlinepubs/9799919799/idx/utilities.html utilities]		*[[User:Rudxain/Unix\|Unix-like systems]], and their [https://pubs.opengroup.org/onlinepubs/9799919799/idx/utilities.html utilities]
	* [[wikipedia:MS-DOS\|MS-DOS]], because it's the common subset among [[Microsoft Windows\|Windows]] systems		*[[wikipedia:MS-DOS\|MS-DOS]], because it's the common subset among [[Microsoft Windows\|Windows]] systems
	* [[wikipedia:C_(programming_language)\|C]]. BTW, there's a C-compiler that makes ''extremely''-portable executables.<ref>https://justine.lol/cosmopolitan/</ref>		*[[wikipedia:C_(programming_language)\|C]]. BTW, there's a C-compiler that makes ''extremely''-portable executables.<ref>https://justine.lol/cosmopolitan/</ref>

	===Interoperability===		===Interoperability===
Line 46:		Line 46:
	Examples:		Examples:

	* [[wikipedia:Zig_(programming_language)\|Zig]], which has "reusable software" as part of its slogan. It also has C [[wikipedia:Interoperability\|interop]]. However, it's still in an [[wikipedia:API#Public_API_implications\|API-unstable]] state, so you'll have to wait before everything is settled.		*[[wikipedia:Lua\|Lua]]. A simple and powerful lang built for embeddability and [[wikipedia:Extensibility\|extensibility]]. It's also '''the''' lang used to make MediaWiki modules.
			*[[wikipedia:Zig_(programming_language)\|Zig]], which has "reusable software" as part of its slogan. It also has C [[wikipedia:Interoperability\|interop]]. However, it's still in an [[wikipedia:API#Public_API_implications\|API-unstable]] state, so you'll have to wait before everything is settled.

	===Archivability===		===Archivability===