Temple Operating System
TL;DR
TempleOS Entire OS is a single developer’s creation, including kernel, compiler, editor, and even the shell
🧩 1. Basic Information
Field | Description |
|---|---|
OS Name | TempleOS |
Developer | Terry A. Davis (USA) |
First Released | 2013 (final named version) |
Latest Version | TempleOS 5.03 (2017, final by Terry) |
License Type | Public Domain |
Supported Platforms | x86-64 (runs only on 64-bit PCs) |
Still Active? | ⚠️ No new development (creator passed in 2018), but community preserves it |
⚙️ 2. Kernel & Architecture
Kernel Type: Monolithic, written entirely by Terry in his own style
Architecture: Pure x86-64 — no support for 32-bit, ARM, or other platforms
No protected mode multitasking — runs in ring 0 for full speed (no user mode separation)
640x480 resolution, 16 color VGA graphics by design (to mirror early PC environments)
🌟 3. Key Features
Entire OS is a single developer’s creation, including kernel, compiler, editor, and even the shell
Uses a unique programming language called HolyC, a hybrid of C & C++ with custom features
Built-in text editor, file manager, command line, 2D & 3D graphics libraries
Includes “oracle” mode for random Bible verse output — Terry viewed TempleOS as a modern-day temple
Boots instantly, very small footprint (under 2 MB ISO)
📈 4. Version History & Important Milestones ✅
Version / Milestone | Year | Description |
|---|---|---|
Early J Operating System | 2003–2006 | Predecessor to TempleOS, laid core design |
LoseThos | 2008 | First named OS by Terry, focused on programming |
Renamed to TempleOS | 2013 | Rebranded as a biblical project — “third temple prophecy” |
TempleOS 5.03 | 2017 | Last major release before Terry’s death |
Community forks | 2018± | Small patches & ports (like Mega64 OS), but no official continuation |
🎯 5. Target Audience & Use Cases
Programming enthusiasts: experiment with low-level OS concepts & HolyC programming
Retro / hobby OS fans: see what a “from scratch” OS by one person looks like
Computer history researchers: unique piece of software culture
Note: not practical for daily use — designed mainly as an art/faith project
✅ 6. Pros & Cons
Pros | Cons |
|---|---|
Incredibly small, fast, boots in seconds | No networking, USB, or modern driver support |
Entire system is easily hackable in HolyC | Runs everything in ring 0 — no memory protection |
Fascinating artistic & spiritual vision | Limited hardware compatibility (VGA only) |
Public domain — fully free to explore | Single-user, single-task focus — no multitasking |
🎨 7. UI Demo & Visuals
TempleOS text-based home screen (command shell & file navigator)
Demo of drawing a simple 3D cube or particles using HolyC’s built-in graphics
HolyC editor window side-by-side with direct compile & execution
Oracle feature printing random Bible verses in colorful text
Small games like “After Egypt” or ASCII maze generators
📦 8. Ecosystem & App Support
Entire system revolves around HolyC scripting, with easy inclusion of graphics and sounds
No third-party package system — every program is built from source inside the OS
Comes with dozens of example programs, games, demos, and Bible references coded by Terry
🔐 9. Security & Updates
Runs everything in ring 0 (kernel mode) for simplicity & speed — no protection from misbehaving programs
No internet stack — cannot be network-attacked (by design, Terry said God told him no networking)
Security handled by physical isolation: it’s an air-gapped, purely local environment
No updates after Terry’s last release; enthusiasts simply keep archiving the ISOs
🌍 10. Community, License & Development
License: Fully Public Domain (CC0 style) — anyone can modify, redistribute, build upon it
Enthusiasts maintain GitHub mirrors & ISO archives (for historical preservation)
Discussed heavily on places like /r/TempleOS, retro computing forums, YouTube channels
Occasionally used in OS design lectures as an example of personal operating system vision
