The 64-Bit Temple Operating System
youtube.com
youtube.com
Terry is schizophrenic and this sometimes make communications tricky, but I'm in awe of how he's developed a complete operating environment from scratch and which is quite different from anything else I'm aware of. Also, I really appreciated the insight this video gave into his motivations for the OS and how he uses it. Thanks for uploading the video Terry, and to morganwilde for posting it on HN.
My only disappointment is there isn't a proper Wikipedia page for this project.
The comments from the dead are rather...enlightening.
It's an achievement on the scale of Henry Darger's collection (http://www.folkartmuseum.org/darger) and perhaps stands alone as an example of "outsider art" in the world of operating system design.
I wnated to make a souped-up, modern 64-bit, C64 so teenagers could do what I did in high school. I had the book Mapping the C64 and I had hours of fun poking and proding around with all the internals of the operationg system for cheap thrills. I wanted to let people control the hardware directly. I wanted something simple, to get your head around. LoseThos is two orders of magnitude simpler than Linux. LoseThos is 135,000 lines of code including my compiler. It is 100% self contained and complete. When I got Linux, I was disappointed because I thought "open source" meant I would have fun messing with the code. Linux tries to support so many architectures and has a main frame operating system, that it's too complex. LoseThos is way way way simpler. Plus it has many innovative ideas. It is not ASCII source code, for example.
Edit: there is a lot of explanation at http://www.templeos.org/Wb/Accts/TS/Wb2/TempleOS.html - I guess I should have asked 'are you only interested in x64, or other architectures too?'
http://www.templeos.org/Wb/Accts/TS/Wb2/LineRep.html
It's written in a C and C++ like language with a heavy helping of assembly thrown in. That sort of thing is usually reserved for embedded platforms where every nanosecond counts, but in this case it's the go-to language. This might be an artifact of how earlier in the project the assembler part was a lot more reliable than the rest of the compiler.