Skip to content

Blog: #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lemanschik opened this issue Dec 5, 2022 · 0 comments
Open

Blog: #5

lemanschik opened this issue Dec 5, 2022 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@lemanschik
Copy link
Owner

lemanschik commented Dec 5, 2022

The history of Holy C and Temple OS

once in a time there where a lonely miss understood dev who was confronted by many ignorant developers.
He wrote his own OS it was Called Tempel OS and he did that alone. You should watch his story google for tempel os and holy c or watch youtube videos to better understand what you see here.

TempleOS is a 64-bit, non-preemptive multi-tasking,[8] multi-cored, public domain, open source, ring-0-only, single address space, non-networked, PC operating system for recreational programming.[9] The OS runs 8-bit ASCII with graphics in source code and has a 2D and 3D graphics library, which run at 640x480 VGA with 16 colors.[5] Like most modern operating systems, it has keyboard and mouse support. It supports ISO 9660, FAT32 and RedSea file systems (the latter created by Davis) with support for file compression.[10] According to Davis, many of these specifications—such as the 640x480 resolution, 16-color display and single audio voice—were instructed to him by God. He explained that the limited resolution was to make it easier for children to draw illustrations for God.[1]

The operating system includes an original flight simulator, compiler, and kernel.[3] One bundled program, "After Egypt", is a game in which the player travels to a burning bush to use a "high-speed stopwatch". The stopwatch is meant to act as an oracle that generates pseudo-random text, something Davis likened to a Ouija board and glossolalia.[5] An example of generated text follows:

among consigned penally result perverseness checked stated held sensation reasonings skies adversity Dakota lip Suffer approached enact displacing feast Canst pearl doing alms comprehendeth nought[5]

TempleOS was written in a programming language developed by Davis as a middle ground between C and C++, originally called "C+" (C Plus), later renamed to "HolyC".[5] It doubles as the shell language, enabling the writing and execution of entire applications from within the shell. The IDE that comes with TempleOS supports several features, such as embedding images in code. It uses a non-standard text format (known as DolDoc) which has support for hypertext links, images, and 3D meshes to be embedded into what are otherwise standard ASCII files; for example, a file can have a spinning 3D model of a tank as a comment in source code. Most code in the OS is JIT-compiled, and it is generally encouraged to use JIT compilation as opposed to creating binaries.[11] Davis ultimately wrote over 100,000 lines of code for the OS.[3]

and thanks to the chromium authors we have a even better os already in our browsers hurray praise the chromium authors and prais frank for sharing with you how ECMAScript Engines work.

@lemanschik lemanschik self-assigned this Dec 5, 2022
@lemanschik lemanschik added the documentation Improvements or additions to documentation label Dec 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant