Last Updated on: 19th October 2024, 11:15 am
Web site: github.com/VoidNV/TempleOS-EE (not active)
Origin: unknown
Category: Desktop
Desktop environment: TUI
Architecture: x86_64
Based on: TempleOS
Wikipedia:
Media: Live
The last version | Released: 6.02-beta | October 10, 2019
Zobacz po polsku: TempleOS Explorers Edition
TempleOS Explorers Edition – a fork of the 64-bit Temple Operating System. Explorers Edition builds on top of the base TempleOS to add new hardware support and installation options.
The initial Goals are to bring the core of the OS up so it can be installed and run on (as many as possible) x64 PC’s
– 32 Bit VESA Graphics
– AHCI Support
– More installation options (Maybe something using LILI style Virtualbox on a USB stick, Grub USB stick with a RAM ISO Image)
– Focus on the core Kernel
– Ability to easily manage code changes in source control
– Add newer OP codes to the assembler and compiler
– Develop hardware graphics driver
TempleOS was developed by the late Terry Davis and is a true testament to what a person can achieve, he single handedly developed and built the OS using a compiler he also developed. The system is “alien” to all its contemparies in that no external code or binary’s can be introduced into the system (easily) or exported and run outside the environment.
The system has two pre-built binary’s the Kernel and Compiler, at bootup the runtime environment is Just In Time (JIT) compiled and executed. The System is fast, the compiler is fast, in VirtualBox system startup time for me is around 0.4 seconds and that includes the compilation time of the runtime environment.
The compiler HolyC is a variant of C and there is some crossover, but there are enough differences that they are not compatible, IMHO HolyC is a better implementation, much more forgiving, more capable as a low level language, more capable as a general language simplified in the engineering sense where is easier to get things done, and it is clearer what is going on so other peoples code is much easier to follow, clearer and simpler in the engineering sense with no unnecessary complexity being added to an already complex domain.
He didn’t re-write the book he built on the lessons of C and created a language which builds on the strengths, removes several complexities and weaknesses. But not all, pointer implementation as far as I can tell is implemented in the same way that it is implemented in C.
