TempleOS: Difference between revisions
No edit summary |
No edit summary |
||
| Line 15: | Line 15: | ||
TempleOS combines a custom kernel, an integrated programming language (HolyC), and an intentionally restricted execution and hardware model. It is frequently discussed as a case where an operating system is best understood not only as an engineering artifact, but as a deliberately constrained system with a narrowly defined internal purpose.{{fn|3}} | TempleOS combines a custom kernel, an integrated programming language (HolyC), and an intentionally restricted execution and hardware model. It is frequently discussed as a case where an operating system is best understood not only as an engineering artifact, but as a deliberately constrained system with a narrowly defined internal purpose.{{fn|3}} | ||
== Footnotes == | |||
<ol style="margin-left:1.2em;"> | |||
<li id="fn-1">...</li> | |||
<li id="fn-2">...</li> | |||
<li id="fn-3">...</li> | |||
</ol> | |||
Revision as of 12:45, 15 December 2025
|
TempleOS | |
|
| |
| Type | Operating system (experimental) |
| Developer | |
| Initial release | |
| Written in | English (HolyC programming language) |
| Platform | |
| License | |
| Status | |
TempleOS is a lightweight, experimental operating system created and maintained primarily by a single developer, Terry A. Davis, between approximately 2003 and 2017.Template:Fn It was designed as a standalone computing environment rather than a general-purpose operating system, with explicit religious, aesthetic, and technical constraints shaping its architecture.Template:Fn
TempleOS combines a custom kernel, an integrated programming language (HolyC), and an intentionally restricted execution and hardware model. It is frequently discussed as a case where an operating system is best understood not only as an engineering artifact, but as a deliberately constrained system with a narrowly defined internal purpose.Template:Fn
Footnotes
- ...
- ...
- ...