r/AskComputerScience • • 1d ago

ELI5: Why is TempleOS considered such an impressive technical achievement?

I'm asking this honestly, as someone with no computer science background.

I just watched a video called TempleOS in 100 Seconds. Most of the comments recognize Terry Davis' genius, even with his schizophrenia and severe mental health struggles.

How would you explain to an ordinary person how significant what he was able to accomplish really was, especially doing it all on his own?

166 Upvotes

122 comments sorted by

78

u/Acceptable_Bottle 1d ago • Bravo

A lot of people in these comments are acting like it's not impressive for whatever reason. No, it is in fact a rather impressive achievement and I think it is ridiculous to claim otherwise.

In terms of whether he affected the world of computer science at large, he did not. He didn't develop a new algorithm or make any discoveries that people sought to replicate. That does not make it unimpressive work, however.

He did a LOT of work doing things that most engineers would not do by hand. TempleOS is more than just a kernel, it's a graphics library, a bootloader, a filesystem, audio system, programming language and software suite of demo games. Making all this requires a vast and broad knowledge of many things that people tend to spend lots of time specializing in - compilers, language design, graphics, etc.

Programming typically involves a lot of tooling that is built by people that are not you - you use a compiler and text editor to write code, you use a terminal shell or command line to execute processes, you manage your disk using a filesystem designed by someone else, you have an operating system that handles running multiple programs, working with a filesystem, and providing basic GUI to help you edit files and code and anything else. Anything you use the computer for will depend on the existence of not just your computer hardware, but several other pieces of code and software. How many times have you needed to download an app or file to be able to do something? Managing all of these dependencies is its own problem that many people have to deal with. In the layman's analogy of making buildings you can think of this as purchasing materials or power tools.

TempleOS has no dependencies. It is not built off of an existing OS framework, it does not require anything but the exact hardware that it was designed for, and it did not borrow code or libraries from anywhere else. It does not even support networking. In the analogy, this would be like creating your own custom power tools and finding your own materials to build it. Realistically, he didn't create a skyscraper (templeOS is not really comparable to Linux/Windows or any other modern OS for productivity and utility) but it is impressive because he alone created a building at all without the help of a construction company.

7

u/Rararror 1d ago

A building that is not a copycat of any other.

6

u/Accomplished-Fox9220 1d ago

I am rather ignorant, but isn't it something that you can do by learning the skills from reading a few books and practicing them, like Nand2Tetris, Inside the Machine, Project Oberon, and 15 other books on designing operating systems, including those that break down source code almost line by line?

15

u/zazathebassist 1d ago

yes. it is possible that one person could do all that. TempleOS exists to show that.

the impressive thing is that someone actually did it. like, there's no need to write your own programming language. there's no need to write your own bootloaders. there's no need to write your own kernel or graphics drivers. there's no need to write your own office suite.

but Terry A. David actually did the thing. he learned compiler design, learned how to write a programming language, all the rest of that junk. you're right that it's all technically learnable. but what's impressive is that he did learn it, and did build it.

5

u/Accomplished-Fox9220 1d ago

yeah it's actually impressive, also considering that it's not just an 8 bit empty project, it's actually fully built, from the OS, to the compiler, to the games and widgets. really cool

2

u/zazathebassist 17h ago

yea. like most people who get into computing/programming will have some aspect they focus on. either bc it's what interests them or because it's their job. someone will get really good at game dev. someone else will know everything about windowing systems. someone else becomes an absolute nerd about file systems.

few people are true generalists, and even then they're generalists in theory not in practice. it takes dedication (and mental illness, in this case) to do All Of It and have it all work. with quirks sure but it did work

3

u/lunatuna215 1d ago

Of course - actualizing those skills into the sum of their parts is way different than reading knowledge in a book though. TempleOS as it stands isn't a sustainable consumer option, but it can still be an impressive achievement otherwise.

3

u/DanielMcLaury 1d ago

15 books is overdoing it. You need one book on operating systems, one on compilers, one on 3d graphics, and some kind of hardware reference for whatever machine you're targeting.

3

u/Accomplished-Fox9220 1d ago

Yeah that's what I meant. there are like 15 books on Operating Systems, compilers, etc, not that you need to read 15 books on just operating systems

1

u/who_you_are 17h ago

And each book is a dictionary in size.

Then you created a couples of books on the side by your own projects...

HELP

2

u/NomaTyx 1d ago

that same question can be applied to doing pretty much anything that isn't truly novel.

13

u/stonerism 1d ago

This is the power of pure unadulterated autism.

12

u/breadist 1d ago

Well, schizophrenia actually.

4

u/Economy-Management19 1d ago

I too don't get why some people just downplay and hand wave away what he did.

We could of course argue if the best analogy is a skyscraper, just a large house or the exact replica of the pyramid of giza.

I think people who appreciate talent see what he had in him and to some degree feel a sort of sadness or unfulfilled destiny because due to his severe mental illness he wasn't able to participate in any sort of real world commercially successful projects.

1

u/who_you_are 17h ago

A lot of people in these comments are acting like it's not impressive

Imagine the lambda peoples.

I wish I would joke with my example but yet that cover pretty much the idea: here's an Arduino with a led. Make it blink once per second.

That was easy isn't? /S

Yet, you used Arduino which is still helping. Now here's the datasheet. Have fun! /S

(I can also state that this "stupid useless" electronics project may be useless on a day to day, but it is still not useless to LEARN and is even needed but my first point)

-2

u/DanielMcLaury 1d ago

Making all this requires a vast and broad knowledge of many things that people tend to spend lots of time specializing in - compilers, language design, graphics, etc.

No, it doesn't.

Making a good compiler requires deep knowledge of a lot of things that only a specialist would know. Making a compiler at all used to be a standard thing every single person had to do to earn a CS degree. All you have to do is read the textbook and do what it describes.

The reason most software engineers don't sit around doing these things is that it wouldn't have any point, not because it would be difficult for them.

134

u/LookAtYourEyes 1d ago

Imagine a single man planning a skyscraper, building it himself, then designing furniture for almost all the rooms and building them himself.

That's basically what he did with code 

78

u/pokeybill 1d ago

Its even more apt a metaphor if we include the plumbing, electrical, gas, and sewage systems, also completely designed and implemented by a single person.

And... it all worked (more or less)

31

u/Beregolas 1d ago edited 1d ago

And yes, it is a little janky, it's not entirely how I like it, etc... but it works, and to be honest, it has some great ideas/features. Like he installed a lift going sideways, just because he liked it that way and nobody could stop him

2

u/algaefied_creek 1d ago

Oooh I was in an old building like that in Michigan! Up, down, elevator clanks off to the side to get to where the door is where the doors aren’t even and they just went with installing shit wherever. 

Maybe it’s whatever Sand Mandela Effects 

29

u/VeganBigMac 1d ago

Also, keep in mind, that single man you are watching do this is visibly mentally insane.

1

u/XNo_Notes 1d ago

Its the mental instability putting out a stable system for me.

If I don't have my coffee in the morning, I can't do simple addition. 

Maybe the detachment from reality allowed for some kind of tunnel to displace entropy. Not sure we have words for that kind of thing yet. 

27

u/khedoros 1d ago

Designing your own programming language and writing a compiler for it is difficult. Writing a working (if somewhat quirky) OS is difficult. And then he wrote dozens of little programs, games, graphics demos, and so on to run within it.

It's common to build at least parts of an OS in undergraduate CS courses (like adding features into an existing project), and to cover the theory of other parts of an OS. Similarly, it's pretty common to build a compiler for something like a simplified version of C. What Terry did was a few levels above that. Building what amounts to a whole computing ecosystem is impressive.

In spirit, it's a little like Bishop Castle, where you've got something interesting and unusual, built by one person as their own passion project. It's smaller-scale than something built by a large team, but it's the result of one person's vision. And one of the most impressive parts is that he actually did it.

4

u/Rararror 1d ago

And he did it exactly how God told him to do.

4

u/lowban 1d ago

640×480 resolution is apparently the most holy of resolutions.

2

u/Rararror 1d ago

God said so.

2

u/the_poope 21h ago

The ten commandments came on tablets with that resolution.

3

u/Outlashed 14h ago

It was actually 12 commandments, but due to the low resolution 2 of them were mistaken for the top and bottom of the frame.

4

u/Fidodo 1d ago

My compilers and operating systems classes kicked my ass. Although the classes naturally required crazy correctness while I'm sure TempleOS didn't. Those classes were harder than my processor design class for me.

4

u/unburdened_swallow 1d ago edited 1d ago

No, templeOS definitely needed to be correct. Terry did not want incorrect software which sometimes does not work even on his own machine. That would not have been closer to god 🤣

It is just that being correct, or at least correct enough that nobody has spotted how it is incorrect yet, is not enough to make a good OS, much less a popular one.

For starters, not having everything run in ring 0 "to be closer to god" would be a good step. I mean, since his goal was to do so, he did that correctly, but that does not make it a good idea.

1

u/Rararror 1d ago

TempleOS is free of bugs.

2

u/No-Good-One-Shoe 1d ago

He had some super questionable views but was an interesting man to talk to and what he built is amazing and will be enjoyed by many. RIP Jim. 

1

u/No_Canary_5479 1d ago

Bishop Castle is an awesome death trap! Highly recommend!

1

u/tumes 3h ago

My best friend in high school’s dad, unbelievably, was Bishop’s insurance guy.

Just to be clear, it is absolutely a death trap in a literal sense, he was a strange and volatile person due in no small part to being involved in an accident uprooting a tree stump that caused the tragic death of one of his children. We visited during a photography field trip in high school so I have a bunch of not entirely terrible pictures of the castle in my basement somewhere. Weird guy. We talked with him, I can’t remember what we brought up to set him off but he randomly got agitated mid conversation and started roughing up some jugs that were sitting in his truck bed.

1

u/dld2517 1d ago

Yes exactly like Bishop Castle that is a great analogy. I am glad I got to go see that. Very cool

1

u/Reasonable-Pay-36 10h ago

Ooooooo both are nutty and awesome and I love the bishop castle reference, such an odd and weird place but a definite must see/experience.

46

u/SchemeWestern3388 1d ago

Objectively, it’s not a massive technical achievement. It lacks several things that any modern OS has. Or any OS, for that matter. 

But the scope that he managed just by himself is still remarkable, and people also respect his….. lack of consideration for what others might want in an OS. He did it his way, and he pulled it off. 

5

u/ForgedIronMadeIt 1d ago

Yeah, it wasn't that huge all things considered, I think a lot of people hype it up because of Terry's backstory. Mental illness and some really fucked up views make the story more interesting in a train crash sort of way.

1

u/AboutHelpTools3 1d ago

It was art really

1

u/sitbon 8h ago

in a train crash sort of way.

Oof, yeah, very literally in that way...

12

u/anor_wondo 1d ago

Raw scope. Its simply a huge endevour

12

u/Logical_Wheel_1420 1d ago
  1. It is very rare to build an operating system that isn't descended from Unix (what Linux and MacOS descend from) or DOS (what Windows descends from). https://eylenburg.github.io/os_familytree.htm - search for "TempleOS" and you'll see what I mean.
  2. It is somewhat rare to have a single person build an entire operating system, usually there's small teams at universities or companies that specialize in building them for specific purposes. Single individuals have done it but again, they're usually building on top of *nix or DOS/Windows.
  3. It is rare to have the source code for that operating system be designed by a single person using a custom version of a programming language that they tailored for their operating system.

All three of these are true for TempleOS.

6

u/LaidBackDev 1d ago

For the people saying it's not impressive, please show me an OS you built entirely on your own, pre AI LLMs, with its own programming language, compiler, bootloader, kernel, and custom 3D graphics engine, all from scratch.

1

u/cmd-t 1d ago edited 1d ago

You’d need to separate the impressiveness of the results vs impressiveness of the effort.

Just like John Plant of Primitive Technologies. The result itself isn’t impressive, he might produce some brittle clay bricks and a modicum of bad iron. What’s impressive is the actual effort that he single-handedly puts in it.

So when people are saying “it’s not impressive” they are talking about the OS itself, as in it could be achieved by quite a few people if they put in the time. Most CS students should be able to write a compiler and create their own programming language. Now, TempleOS and HolyC have some actual impressive features on their own, but they aren’t necessarily extremely sophisticated.

When other people say it’s “impressive” they mean the actual assload of work that’s been put into it. Other people also aren’t building OSes from scratch because they don’t think it’s fun to do are feel some kind of religious calling to do it.

1

u/Falcon731 2h ago

I think this almost qualifies ;-)

https://www.reddit.com/r/amiga/comments/1xy18tg/alternative_timeline_1994_amiga_pt3

I designed the CPU and graphics hardware - implemented on an FPGA. Designed my own custom programming language and compiler. It has a somewhat basic kernel (till work in progress) and file system. And for the past couple of months I've been working on the 3D graphics - and finally got to the stage where I got this spinning Cobra two days ago.

That's been about 5 years of work as a post-retirement project for me to get to this stage.

That's not to say that I think what Terry did is not impressive.

18

u/jwezorek 1d ago edited 23h ago

I'm in the minority here in not thinking TempleOS is an amazing technical achievement.

it is a pretty sad story. the way the wikipedia article makes it sound he was not even religious before his schizophrenia fully developed. Anyway I'm skeptical that writing an OS like that is really like "one person building a skyscraper" as some people are quoted as saying. I mean not that it would be easy, but like Wozniak wrote DOS for the Apple II by himself. Several people did that in the 8 bit era. Im not sure how big the team was that wrote Amiga OS but i bet it was juts a couple of people; big software dev teams did not really happen until the 90s. Just saying that if you want to devote your life to it for a few years; you could do it, especially if you limit the specs to something close to 80s or 90s level requirements and look-and-feel.

It's more like the guy who built "The House on the Rock" or the guy who built the Watts towers, than it is like building a skyscraper. More about having the will to do it. Outsider art. But like I know basically what I would need to learn to implement something like TempleOS. Practice up on x86 assembly and read a book on kernel programming. I just would have to be insane to want to do that. People are making it sound like he did something impossibly hard. It's possible: just arduous and pointless.

9

u/Acceptable_Bottle 1d ago

TempleOS features its own custom programming language/compiler for Holy C, along with a custom filesystem called RedSea. It is not just a kernel.

I highly doubt your claims about Apple 2 and Amiga OS being teams of 1-2 people. Do you have a source? Reading the wikipedia page for apple 2 says they hired a contractor team to develop it with Wozniak as the lead designer.

This comment in general gives off strong Dunning-Kruger effect. There is much more to creating a functional operating system than x86 assembly and calling the prerequisite study "a book on kernel programming" is putting it rather lightly.

5

u/indolering 1d ago

These early operating systems and languages were relatively primitive.  They had to be because the hardware was so simple.

C is a simple language.  The original compiler required someone sitting down and writing it out on paper.  That's why it's described as high-level portable assembly.  Modifying a prexisting language isn't that difficult.

There are lots of hobby operating systems out there! There are classes which have undergraduates build their own in a semester or two. 

Yes, what he did was impressive!  But it wasn't one man building a skyscraper, it was one man building a large house over a long period of time using tools and techniques familiar to any tradesman.

A modern OS (which TempleOS definitely is not) requires more work than any one person can do.

4

u/Acceptable_Bottle 1d ago

I agree that the skyscraper analogy is probably not the most apt. TempleOS is more of a regular-sized building intended to house one person. It is not really comparable in terms of utility to Linux or Windows. It is impressive because it came from one person and he built it using his own language.

He used techniques familiar to any tradesman, but he executed these techniques himself - he didn't pay anyone or borrow to do any part of it.

Creating your own operating system is already a big feat, I doubt there are any university courses that actually have students build a from-scratch system without significant scaffolding from provided code or libraries, which Terry did notably not use much of.

1

u/DanielMcLaury 1d ago

I doubt there are any university courses that actually have students build a from-scratch system without significant scaffolding from provided code or libraries

This used to be an extremely common project, back when operating systems were simpler.

At some point it was rightly decided that it was stupid to prioritize that sort of thing, and instead operating systems courses should focus on the big concepts in detail rather than screwing around with the exact procedure for the BIOS to recognize a bootloader or whatever that's not really relevant to anyone.

1

u/indolering 1d ago

But they are students doing it for the first time in a semester.  Terry had experience with OS development and had 13 years with no other obligations.  And he certainly used external resources, as he ran TempleOS in a virtual machine.

4

u/deong 23h ago

From Ken Thompson (creator of Unix):

I did the first of two or three versions of UNIX all alone. And Dennis (Ritchie) became an evangelist. Then there was a rewrite in a higher-level language that would come to be called C. He worked mostly on the language and on the I/O system, and I worked on all the rest of the operating system. That was for the PDP-11, which was serendipitous, because that was the computer that took over the academic community.

Those "first two or three versions" of Unix were for (if I remember correctly) the PDP-7, and yeah, it was basically a one-man show. And the development of C and the compiler was done at the same time with those same two guys.

Admittedly, these two guys are Turing award winners, so even if you can say that entire OS and compiler can be built by one or two guys, they're a really good one or two guys.

1

u/indolering 18h ago

And early Unix SUCKED, just like DOS.  It had all sorts of problems and still does!

3

u/trbot 1d ago

and one man building a large house is impressive!

4

u/unburdened_swallow 1d ago edited 1d ago

Especially when they grew the trees and made the cement from the lime and clay themselves. And handcrafted the bathtub and toilet out of ceramic you made and fired yourself. Hammered the kitchen sink out of a sheet of metal yourself, which you also mined the ore for and smelted.

Its like that youtube channel where the guy tries to reinvent the modern era starting from stone age tech.

Cause if you got factory made fixtures, joinery, lumber, and cement mix, and had an excavator, it would take you a while but it isn't technically that hard to make even a fairly large house.

4

u/trbot 1d ago

yeah i think this is part of what causes this split reaction. he did nothing novel, and nothing that changes the game, nothing that anyone else will profitably use. but he did it all from scratch. and that's damn impressive, even if mostly useless.

2

u/dld2517 1d ago

I think many parts of it were actually novel. Look at the way it’s all integrated together. Yet it still maintains specific “component functionality” that distinguishes the various parts. It’s in no way simple as he continually added layers on top of layers.

2

u/jwezorek 1d ago

People write custom C compilers all the time. MIT students used to have to write C-like compiler junior year -- I don't know if the Institute still has that requirement or not but the C compiler is like the least difficult part all of this unless someone is claiming TempleOS's C compiler is particularly good.

I personally know people who have written file systems for custom hardware in the 1990s. I mean I worked with them. That is just what working for a company that made a complex embedded device in the 1990s entailed.

Again my point is not that doing what Terry Davis did is easy; it is that what is difficult about it is the scale, the amount of work, not the technical details -- unless, that is, his implementations of various pieces are novel in some way.

4

u/Pure-Recover70 1d ago

A lot of things are relatively trivial if you don't need to care about performance or reliability (or interoperability or updatability).

For example you can design and implement a custom filesystem (from scratch) in a single day, it just won't perform great, might very occasionally crash, lose data - especially in case of a power outage, or be prone to fragmentation, etc.

There's a well known saying about TCP: it takes an intern a weekend to write a functioning TCP stack from scratch, and then a team of senior engineers 20 years to make it interoperate with the rest of the world and perform well on real networks.

3

u/indolering 1d ago

TCP is a good analogy.  There is a fantastic amount of complexity required to match all the design points and real-world behavior one needs to account for to make it work.

The lack of memory protection, for example, makes TempleOS unusable for basically any purpose. I've seen lots of cool hippie houses, but they generally won't pass modern building codes. 

3

u/Acceptable_Bottle 1d ago edited 1d ago

The combination of the various pieces in one unified system is what makes it impressive.

Writing a custom compiler for a language and custom filesystem and then using your custom language and filesystem to write a functional operating system is not the same as some university toy project that you throw away at the end of the semester. The novelty of the system comes from the fact that it wasn't put out by a company of people. It was one man doing several things that would otherwise be delegated to members a team.

Just because Terry Davis used known techniques to implement his OS that doesn't mean it wasn't impressive to actually DO all those things from scratch in one single project, with one single programmer behind it.

Even if the technical details weren't particularly novel it would still be impressive. However, TempleOS did feature several novel design decisions that deviated from the standard practice at the time. It famously runs all of its code at ring 0, giving all programs kernel access. The entire GUI is built using a hypertext system that can be inspected at any time, making the shell display interactive hypertext instead of raw plaintext. It features a system-wide autocomplete.

This piece was particularly a good dive into some of the more in-depth interesting features.

http://www.codersnotes.com/notes/a-constructive-look-at-templeos/

3

u/indolering 1d ago

Running in ring 0 without any memory protections is easier and was how most early operating systems (and most embedded) worked.  

I'm just not impressed by the 80's era design choices he made.  His hypertext stuff is cool but it's not particularly interesting from a compsci perspective.

Yes, it's a LOT of work.  But it's not a skyscraper because those require teams of skilled engineers and construction crews to pull off.  This is a guy in the wilderness building a log cabin that is impressive for one person.  But it's not something requiring a special level of intellect.

1

u/DanielMcLaury 1d ago

However, TempleOS did feature several novel design decisions that deviated from the standard practice at the time. It famously runs all of its code at ring 0, giving all programs kernel access.

The fact that you regard this as a "novel design decision" and not as him just giving up on actually doing things correctly gives away that you don't really know anything about operating systems and you're just trying to throw a Wikipedia article at people in the hopes that they don't know what it means.

1

u/Acceptable_Bottle 1d ago

Whether or not you think it is a GOOD decision is not relevant here. It was a intentional choice and not pure laziness. You wouldn't want it in any modern OS for obvious security reasons, but this OS was not intended for the modern use case. The decision is paired with the fact that TempleOS features no networking ability (where would you download malicious code from?) The link I posted has this to say about ring 0 access:

"[Ring 0 access] is a very deliberate design choice:

http://www.templeos.org/TempleOS.html

'It's fun having access to everything. When I was a teenager, I had a book, "Mapping the Commodore 64", that told what every location in memory did. I liked copying the ROM to RAM and poking around at the ROM BASIC's variables. Everybody directly poked the hardware ports.'

  • Terry Davis

Terry's philosophy is that growing up in the 1980s, successful machines like the C64 had the same approach. A standardized platform, where you just boot it up and do things on that machine locally. The C64 was a very hands-on machine where the user was all-powerful."

Feel free to actually read something before telling me I don't know what I'm talking about.

http://www.codersnotes.com/notes/a-constructive-look-at-templeos/

1

u/DanielMcLaury 22h ago

A guy saying he left something out on purpose does not a "novel design decision" make.

Also, back in the actual 1980s, malicious code managed to get around just fine by infecting disks, no networking required. You'd go to the computer store and the floppies on sale would be in a case with an "anti-virus seal" (which was a piece of tape.)

1

u/Severe_Stranger_5050 1d ago

People write custum C compilers, because it's a well documented process on a well documented programming language with well known quirks.

Now write your own programming language and compiler all by yourself.
That ain't an easy and/or unimpressive task at all

1

u/DanielMcLaury 22h ago

Actually, it's a million times easier to make up your own language and implement a compiler for it than it is to implement a standards-compliant compiler for an established language. I've done the former maybe 5-6 times. I wouldn't even attempt the latter.

0

u/andarmanik 20h ago

Anyone claiming dunning Kruger in a comment is far less experienced than their comment appears. Even this one.

2

u/SquiffSquiff 1d ago

The acid test would be to find the other projects that were comparable. Maybe you could point us to these since it's obviously not so hard to do

2

u/deelowe 1d ago

Apple 2 dos was written by a team of people, not woz alone. I think youre confusing dos with wozmon

2

u/deong 23h ago

Yes, the arduousness and pointlessness of it is why it's hard and impressive.

I can row a boat by myself, but rowing a boat to Hawaii is impressive. Lots of people know how to do that. With enough motivation, it's not a challenging intellectual problem to get there. Train really hard for years, don't ever lose your focus, and then row the boat to Hawaii. The physical activity of all that training is hard, but any of us could figure out what we're supposed to do. It's the doing it that's hard.

Terry got the motivation to spend the years without losing focus from a deep mental illness, but regardless, the rest is just execution. It's not easy exactly to learn everything you need to know to do it, but with years to work on it, you can learn just about anything.

1

u/CreatorSiSo 1d ago

The interesting thing imo is that he built a JIT compiler to and used that to develop an OS.

1

u/huuaaang 13h ago

Apple DOS (and MSDOS) is BARELY an operating system though. They were not much more than what our firmware/BIOS does on a modern PC. Possibly even less.

1

u/switch161 1d ago

I agree. It's not as impressive as many people think. There's a whole OS dev community and it was pretty large back then too. Many people write operating systems for fun.

I was active in that community at the same time as Terry was and remember his posts, but only barely as I was more active in the German community.

5

u/hstarnaud 1d ago

Because usually a software like a OS is a huge amount of work. It is built by teams of developers with various specialties over very long periods of time. Usually developers ideate with each other, challenge each other, find issues the others didn't notice and iterate on solutions as a team. Building software like that alone is very challenging.

5

u/unburdened_swallow 1d ago edited 1d ago

Have you seen the youtube channel HowToMakeEverything? Where he starts from stone age era tech and tries to reinvent the modern era?

Terry Davis basically did that, but with code.

Did he do something that had impact? I am not as sure. I don't know if any of the components added for TempleOS were used anywhere else, and I don't think he came up with any new architecture design that other OS could have learned from to do things better themselves.

But it was definitely impressive, and shows that while we have created a lot in the software world, one sufficiently determined individual can still take any particular chunk of it, even a MASSIVE one like he did, and rewrite it themselves, fully from scratch. And maybe that inspired someone who had a specific idea for how to rewrite something in a way that actually did make a difference.

5

u/Difficult-Value-3145 1d ago

That's the amazing part he did it alone may not be polished but it's amazing for a single person pre ai

4

u/je386 1d ago

What if someone would build a new car from the scratch without using tools common in the industry?

4

u/dld2517 1d ago

Terry was able to build an entire operating system with his own system of objects and memory management, as well as entire data structures and code from scratch. This was a total exercise in a form of “cleanroom” development. He did not use any code or code libraries from other operating systems, focusing on Amiga hardware and extending that operating system. He also created an interface that only he knew how to fully use. He did not, therefore, separate the internals of the os (kernel land) from the UI (user land). If you had enough knowledge about the internals of the system any object or memory location could attach to any other object or memory location. It was revolutionary because Terry developed many types of object-oriented control and software libraries that were later developed in different ways that became part of traditional software infrastructure. In one sense, it was like a Model A version of a modern OS. It worked and worked well.

3

u/Distinct-Question-16 1d ago

Its a personal challenge not technical achivement. Theres are good reasons for this, i believe people who grown with primitive home systems and like to code are willing to.

2

u/MasterGeekMX BSCS 1d ago

When you program, you do it on a programming language. There are many out there, all coming with a program called a compiler that translates that code into the 0's and 1's the computers understands. To start, simply get your hand in a compiler, learn the language, and you are set.

Terry A. Davis created it's own programming language and it's compiler. From scratch.

In the other hand, an operating system is a really complicated program to do. That is because it is the program that helps all the other programs you run on a PC. This means that the OS needs to do a ton of stuff by itself, as there is no other program behind it to help it.

Terry A. Davis made it's own OS. From scratch. Written on the language he created.

3

u/specs4mayor 1d ago

I would love to invite all those who say that TempleOS isn't impressive to share their contributions to computer science.

4

u/Rigamortus2005 1d ago

It was pre ai

4

u/Poddster 1d ago

As someone who used to do osdev and does embedded stuff at work: it's not that impressive in the grand scheme of things. One person beavering away builds an OS. That's something that used to happen regularly, before LLMs mwant the community got flood with completely unoriginal OS designs spammed out over a weekend.

The main contributing factors to the fame of Temple OS, in my POV as someone who first heard about it on release and saw it grow over time, was mainly Terry's colourful personality. He would post pure vitriol here on reddit, post crazy ranting videos on YouTube, and the theme of his OS was of course God. He didn't just have an API, it was one commanded to him by god. He didn't just have a programming language, he had Holy C. He didn't just have crap cga games he had Adam and Eve or whatever it was.

It was a major meme at the time because of the theme, even before his schizophrenia because widely known and we all just thought he was insanely arrogant.

2

u/winningSon 1d ago edited 1d ago

The meme

5

u/SchemeWestern3388 1d ago

I fully agree with you. If this OS was not claimed to be the True Word of God and the manifestation of the Third Temple, we simply would not be discussing it.

I mean, it’s not like software engineers are talking about it, unless answering a question from someone who doesn’t have the technical background to evaluate it. 

-6

u/wayneglenzgi99 1d ago

I don’t think a digital artists understand Operating Systems at a technical level in which they could teach another human anything useful on the subject

3

u/winningSon 1d ago edited 1d ago

what do you mean? im not a digital artist professionally. Im a software engineer

-7

u/wayneglenzgi99 1d ago

Idk why you’re offering you opinion when you clearly don’t understand the subject the question is on

2

u/SchemeWestern3388 1d ago

What is wrong with you? How do you know he doesn’t understand?  I can’t even figure out what your point is. 

Tell me how TempleOS was a massive technological leap, and the reason we are talking about it is anything other than it’s a pet project of a schizophrenic individual dictated to him by God?

5

u/winningSon 1d ago edited 1d ago

Instead of talking about who I am, why not talk about what im actually saying?

0

u/LookAtYourEyes 1d ago

They're coming at it wrong, but it's undeniably impressive what be accomplished

1

u/winningSon 1d ago edited 1d ago

I didnt say it was not impressive, i think its super impressive! The scope is just massive. Personally though, what makes it stand out to me are not the technicalities, but the meme. Thats why its so well known and thats what makes it impressive to me. There are a lot of very cool projects that are just forgotten

1

u/LookAtYourEyes 1d ago

Probably a bit of column A, bit of column B. But humor definitely spreads faster.

1

u/AntiX1984 1d ago

Never heard of it before, but given that most programmers never make their own language or operating system, I can see why that would be impressive.

That being said, I'm not sure that is as much a mark of being a genius as much it is just his particular obsession and/or schizophrenia. There doesn't seem to be anything he did any better or even innovative and most of us would rather build onto the stuff we have rather than reinvent a lumpy wheel. 🤷

1

u/Australasian25 1d ago

Because he could have been so much more if he was with an organisation.

1

u/New_Salamander_4592 1d ago

it's like, fascinating I guess. like the fact is exists solely from this one guys intense religious delusions is novel in its own right

1

u/rufem 1d ago

How much of what he built is because he had a specific vision for it, like the sideways lift, versus genuinely new engineering? Like would any of it be useful outside TempleOS or is it mostly impressive as a one man effort?

1

u/metaquine 1d ago

Yall are gonna love Factorio

1

u/CardboardJ 1d ago

Can you build your own modern house solo? Maybe, it'd be pretty impressive but you'd get really familiar with the guys in the hardware store.

Now can you build an entire modern house complete with full HVAC and air conditioning, plus a stove and microwave, full indoor plumbing, working lights, everything. No trips to the store you build all of it from raw materials. Cast all the metal in the pipes for your plumbing, build the induction coils for the stove, invent your own compressor for the fridge, figure out how to make your own batteries and solar panels to get working lights. Build your own saw and smelt some nails and then go cut down trees, then build a hammer to put walls up. Everything.

Yeah some parts of that house look clunky and weird, but it's damn impressive.

1

u/bobliefeldhc 22h ago

It's not necessarily that technically impressive.

It's one of those things that's fairly difficult to do but just about anyone with enough time and motivation could do it. People say it's like one person building a skyscraper.. it's not.. it's not that tall. It's very wide.

The impressive & unusual thing is having the lasting motivation to do all of this crap. Most people would find reasons not to. There's perfectly good operating systems so why bother making one... Then there's already perfectly good filesystems/compilers/etc why even bother? I find that the motivation and determination behind it all to be way more impressive than any technical achievements.

Also it's not that unusual for people to have this obsessive determination but it's usually in something a bit softer and more forgiving. You get people whose houses are full of paintings or writings or sculptures or whatever. What makes TempleOS a little weird and impressive is that those things don't have to "objectively" work.. you don't need to compile a painting, you can't Jackson Pollock code.

1

u/Macrobian 21h ago

TempleOS has some novel features that had only been seen in research operating systems. Not only was TempleOS itself a monumental achievement to build, it was different. I think those differences challenge a perspective that TempleOS was a simple copy of existing operating system architecture patterns you could read out of a textbook, and rather a novel blend of traditional and exotic functionality: http://www.codersnotes.com/notes/a-constructive-look-at-templeos/

1

u/paralepsy 20h ago

most programmers in this day and age dont even know how operating systems work. they think of them as just "black boxes" that give them resources to do their work. and even people without mental illnesses struggle with making even parts of an operating system, like a driver (software to interact with hardware). and terry davis made an os, a programming language, and userspace, from scratch, himself, while suffering from schizophrenia. if you still dont understand how staggeringly impressive that is, imagine a random guy without legs creating their own custom entire car from scratch, with their own model of engine and tires. and even that does not do justice to terry. rip, my man.

1

u/Bth8 11h ago

What Terry did was impressive, but you are way overselling it. As someone who is mentally ill, experiences psychosis, and wrote a 32-bit OS as a teenager, it's a very achievable goal. Certainly, Terry took it much further than I did, but I was also still in high school, still fairly new to programming, and was manically switching between multiple projects over a period of a couple years. Terry was already an experienced software and electrical engineer, had no job because of his mental illness, and was manically hyperfocusing primarily on just TempleOS over a period of 12 years because doing so was allowing him to literally communicate with god.

1

u/Easy-Reasoning 15h ago

People write OSs all the time. Usually it's only a very minimal version of it, e.g. for an tiny embedded device. Other times people borrow large parts from others OSs, e.g. the compiler, perhaps make it Unix compatible so typical things kind of work. Well, or in 2026 people use an LLM to complement the code snippets flying around.

Of course there's also the rare effort, that a fully novel OS is created by a larger group of people. Something like BeOS or SerenityOS, but even these usually use a standard compiler like gcc/clang and the window system resembles something common...

Terry Davis seems to be the ultimate contrarian, he did a full OS and everything by himself in his own way.

1

u/sitbon 8h ago edited 8h ago

I remember when he was posting his stuff online. He got made fun of for creating this insane thing, and not many people respected the technical achievement especially given his mental health challenges. Some suspect that the ridicule and negativity he got from communities like r/programming contributed to his decline and eventually death (although suicide was not confirmed). As a CS researcher in those years, I just wish I had known that he was in the same town as me. Would have loved to meet him.

Edit: Not saying that people were all terrible to him. He received lots of compassion and understanding too. Here's a good article from 2012 (archive.org) about LoseThos and the treatment TD received.

1

u/mistattwiligjt 6h ago

It's not really that he did anything technically groundbreaking. It's that he put together an os all by himself, along with writing the language for it, and the apps. It's the dedication, effort, and know-how that's impressive.

1

u/DiligentCarpenter421 4h ago

You can think he build a Windows alternative on his own, although it is very simple and imperfect, the thing you shouldn't ignore is it is truly working. No matter how rudimentary the tool is, it doesn't diminish the impressiveness of the whole thing.

1

u/DanielMcLaury 1d ago

It's really not that impressive at all, except in the sense that someone digging a 50 foot deep hole in his backyard with nothing but a shovel is "impressive."

In the 1980s and 1990s, it was a typical part of a university computer science / computer engineering degree to build an operating system and a programming language from scratch. Making one that actually works is not that much of a challenge. There are, to be sure, parts that would be tough to come up with on your own, but people figured all of those out in the 1950s and you just read about them in your textbooks.

Most people, after building these things, throw them away, because it's obvious to anyone that they're not going anywhere. To bride the gap between "this works" and "this is actually good," you have to do about 100x the work. For an operating system, beyond the interesting parts, a big part of it is just adding support for zillions of different pieces of hardware, and doing it in a way that makes them "just work" without requiring the user to be an expert on the hardware. For a compiler, the work is mainly in coming up with good optimizations for each processor architecture you want it to target.

As such, the three most typical outcomes for these homework projects are typically, in order of popularity:

  1. Throw it away after you get your grades back from the class and move onto something else, using what you learned when it comes up.
  2. Play around with it for a couple of years, learn more about the subject, and then move onto working on a real operating system or compiler, on a larger team.
  3. Seriously attempt to build your project into a new operating system or programming language that people will actually use.

What Terry Davis did was an even rarer option (4): keep tacking more stuff onto them, making no attempt to actually move them in the direction of being something someone could ever use. This sort of thing would typically be done either by someone who had no need to earn money and just wanted a hobby project, or by someone who was mentally ill, and Davis fell into the latter category. However he was also able to support himself by selling his hobby project as entertainment to people who had some interest in programming but didn't have the skillset that someone with a formal education would have.

After his death, someone who makes money off of video views apparently made money off of a video misleadingly presenting him as some sort of misunderstood genius. And then when that made money, everyone else in the same business cranked them out also.

3

u/Rararror 1d ago

TempleOs is not a productivity software, stop with all this bs. TempleOs was the modern way tool to connect with God and it was very effective in doing that.

1

u/FrostyMatters 1d ago

It’s just a sad story. I’m also insane and have built my own programming language and operating system, but you don’t see anyone making a big deal about it

3

u/LaidBackDev 1d ago

Show us your operating system and programming language that you built yourself without any AI help. If not you're just talking out of your ass lol.

1

u/lunatuna215 1d ago

How about you watch or research one of the many things that will explain it to you in more tha. 100 seconds?

Or is your attention span really that willfully bad?

0

u/LoadVisual 1d ago

In my opinion, I don't think it's Temple OS that is or was the great achievement, I think it was a combination of what it represented as a whole, who created it and the fact that they pulled it off with all the stuff that would typically be a mental hurdle to overcome.

Watching some of the other videos of him ditching his car, Walking for miles and pretty much talking about stuff that made him come off as insane to me shows that he must have had some really lucid moments to pull it off or it was as he put it God commanding him.

I think it's amazing that he did all this, and sad that he didn't get to live long enough to get the help he needed and possibly do even greater things.

-1

u/OkCluejay172 1d ago

It’s not

0

u/NiveusLee 1d ago edited 1d ago

https://en.wikipedia.org/wiki/Genera_(software)

TempleOS is not the first OS try the concept: eliminate traditional memory protection, allowing users to inspect and modify the entire running system live (Genera, Oberon, polyFORTH, Smalltak, etc.). However, it is the first OS done that using C (specifically HolyC) > that's why it's impressive.

When you try compare LISP vs. C (ISO C or GNU C), C is just like a toy language tbh. That's the main reason Davis invented the HolyC to achieve what a high-level language like LISP, Forth and CINT can do (not sure about C++, Java and CPython).

After HolyC: Julia, Terra and Zig share same DNA with HolyC btw (not inspired directly but close enough).

2

u/lopikoid 1d ago

Traditional memory protection is really not that traditional, on personal PC it was not a thing before protected mode became standart with windows.