TempleOS - The 64-Bit Temple Operating System

TempleOS discussion thread

http://www.templeos.org/

TempleOS is 64-bit, flat, non-segmented and multi-cored. It's like a modern, souped-up, multi-tasking, cross between DOS and a Commodore 64. It has a C64-like shell with HolyC, a dialect of C/C++, instead of BASIC. It was written from scratch, and not even ASCII was sacred -- it has 8-bit unsigned character source code to support European languages. Also, the source code has graphics.

"You get out of god what you put in"

* The 64-Bit Temple Operating System: https://www.youtube.com/watch?v=EViG0Q4lTeA
* Mom tries out TempleOS: https://www.youtube.com/watch?v=6WgOWrT1yyI

6:21 So Solomon overlaid the house within with pure gold: and he made
a partition by the chains of gold before the oracle; and he overlaid
it with gold.

6:22 And the whole house he overlaid with gold, until he had finished
all the house: also the whole altar that was by the oracle he overlaid
with gold.

6:23 And within the oracle he made two cherubims of olive tree, each
ten cubits high.

http://en.wikipedia.org/wiki/OS/400
IBM designed IBM i as a "turnkey" operating system, requiring little or no on-site attention from IT staff during normal operation. For example, IBM i has a built-in DB2 database which does not require separate installation. Disks are multiply redundant, and can be replaced on line without interrupting work. Hardware and software maintenance tasks are integrated. System administration has been wizard-driven for years, even before that term was defined. This automatic self-care policy goes so far as to automatically schedule all common system maintenance, detect many failures and even order spare parts and service automatically. Organizations using i sometimes have sticker shock when confronting the cost of system maintenance on other systems.[1]

Another peculiar feature is that this system was one of the earliest to be object-based. Unlike traditional OSes like UNIX and Windows NT there are no files, only objects of different types. It implemented one of the earliest-known systems for persistent objects. Further, the objects persist in very large, flat virtual memory, called a single-level store.[1]