( MysteryKe | 2018. 09. 11., k – 09:46 )

How much support code does it take to open a window and draw graphics into it on your operating system? In TempleOS, there is a one-to-one correspondence between tasks and windows, so a single call to DCAlias is enough to return the device context for your window. You can just do this as soon as your main function is called and draw into it. Making a window is surely the most important thing for a windowed operating system - why does it have to be hard? GDI, X11, DirectX and OpenGL could all learn something here.

Hardware & Security

There is no hardware support. By that I mean that TempleOS does not support any hardware other than the minimal core system that makes a PC. There is no support for any graphics card other than VGA, there is no support for any soundcard other than the PC speaker, and there is no support for networking.

TempleOS does not use memory protection. All code in the system runs at ring 0, the highest privilege level, meaning that a stray pointer write could easily crash the entire system. This 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'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.

[...]

TempleOS has no file permissions. After all, if there's only one user, who else could you give permission to? To be honest, I've often wondered if Unix wouldn't be better if we just made all security happen at the mount level, instead of micromanaging it per file.

There are no such things as threads in TempleOS, as it doesn't need them. Processes and threads are the same thing, because there's no memory protection. If you need something in parallel, just spawn another process and let it share data with your own."

Amúgy vannak benne érdekes és egyedi megoldások, de ha az összképet nézzük, akkor egy katyvasz, nehéz eligazodni benne. Az egész inkább mérnöki, egy átlagos felhasználó soha nem fogja használni, de még fejlesztő sem. Az, hogy minden fájl egy dokumentum, az azért zavaró (az ötletes, hogy a szöveges fájlok is tartalmazhatnak linkeket), de hogy a konfigfájlok is tulajdonképpen forráskódok és azok tartalmazhatnak képeket is, az teljes agyrém :D Azt pedig nem tudom, hogy honnan jött neki, hogy tankos-lövöldözős játékot építsen be a rendszerbe, nem tudom, hogy Isten ezt mikor sugallta neki :)
Meg az volt nekem még első ránézésre a zavaró, hogy minden megnyitott ablakban villognak a kurzorok és hirtelen azt sem tudod, hogy melyikben vagy, meg highlight-olnak a menüsávon a gombok, az alkalmazásokban, a parancssorban, plusz az ablakok címsorában és központi sávon is megállásnélkül scrollozódnak az infók......... bele lehet hülyülni :)

Érdemes figyelni a reakciókat:
https://www.youtube.com/watch?v=6WgOWrT1yyI