Philosophy
Small. Direct. Honest.
TempleOS is one person's idea of what a personal computer should be. We keep what makes it special, add protection around it, and say plainly where we fall short.
A motorbike, not a truck. Lean too far and you fall.
Terry A. Davis compared operating systems to vehicles. In his picture, Linux is a semi-truck with many gears, built for shared mainframes with many users, where one crash must not take everyone down. Windows is a car. TempleOS is a motorbike.
| Truck | Car | Motorbike | |
|---|---|---|---|
| Built for | Many users sharing one machine | Everyone, every task | One person at their own computer |
| Safety net | Layers of isolation and permissions | Layers, and many prompts | None. Everything runs at ring 0 |
| Cost of a mistake | Contained | Usually contained | The whole system |
| What you get back | Protection from others, and from yourself | Compatibility | The whole machine, and nothing in between |
A paraphrase of his analogy, as retold in a developer walkthrough. The table is our summary, not his.
One thing, not four tools.
The shell, the editor, the documentation and the file browser share one hyperlink system. Compare a modern setup, where a terminal, a file manager, an editor and a documentation viewer barely know about each other. Our desktop keeps that spirit: one toolkit, one theme system and one text engine under every window.
Live, not built.
The compiler is the shell. Code compiles as you type, there is no linker and no object files, and the whole symbol table stays live. That loop is the most valuable thing we inherited, so every decision protects it: a change reloads in about twenty seconds, and the compiler itself rebuilds in about three. We refuse tools that would trade it away.
Small enough to understand.
One person built the whole system. A reader can hold it in their head, and every app here is one file. That is a feature to defend. When something would make the system bigger than one person can understand, we ask whether it is worth it.
Part of a lineage.
Writers have compared it to research systems such as the Xerox Alto, Oberon and Plan 9, which blurred the line between programs, documents and the shell. Those systems did not win the market, but their ideas turned up elsewhere. We think some of TempleOS's ideas are worth carrying forward, whatever one thinks of the rest of the story.
One corner of TempleOS, its random-word and random-music oracle, came from its creator's beliefs and his illness. We do not share those beliefs and we do not claim what he claimed. What we do respect is the engineering care he put into making randomness truly unpredictable.
Our rules.
What we add to the original idea.
- Keep what makes it special
Direct drawing, a live compiler, one language, one unified feel.
- Add protection around it, not inside it
Signed packages, permissions and approvals live on the host. The guest stays simple.
- Measure before claiming
Every speed claim has a number, from a named machine, and says what was not measured.
- Ask. Never assume.
Anything outward waits for a decision you can see.
- Open by default
The system, the notes and the plans are readable, including the parts that are unfinished.
- Say what is not done
Status chips and an honest list of limits, on every page that needs them.