tristan/ZealOS
1
0
Fork 0
mirror of https://github.com/Zeal-Operating-System/ZealOS.git synced 2024-12-27 15:56:30 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Update Charter to add Roadmap 'fully-functional self-reproducing' goal, delete Roadmap.

Browse source
This commit is contained in:
TomAwezome 2022-10-30 20:36:50 -04:00
parent ddeca74589
commit 6622e0f624
2 changed files with 3 additions and 26 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
src/Doc/Charter.DD
View file

@ -7,7 +7,7 @@ $FG,5$$WW,1$$TX+CX,"ZealOS Charter"$$FG$
* Low line count and low code complexity is the highest good, so it is easy to learn the whole thing. Users should see the light at the end of the tunnel. * Low line count and low code complexity is the highest good, so it is easy to learn the whole thing. Users should see the light at the end of the tunnel.
* There is a limit of 100,000 lines of code for all time, not including applications and demos. Currently, there are $TX,"98,641",D="DD_ZEALOS_LOC"$ lines of code. $FG,4$3rd party libraries are banned from being required$FG$ because they circumvent the intent of this limit. The vision is a Commodore 64 ROM -- a fixed core API that is the only dependency of applications. Dependency on components and libraries creates a hell that is no longer blissful. * There is a limit of 100,000 lines of code for all time, not including applications and demos. Currently, there are $TX,"98,661",D="DD_ZEALOS_LOC"$ lines of code. $FG,4$3rd party libraries are banned from being required$FG$ because they circumvent the intent of this limit. The vision is a Commodore 64 ROM -- a fixed core API that is the only dependency of applications. Dependency on components and libraries creates a hell that is no longer blissful.
* The primary metric for resolving all ZealOS code governance issues is how fast the compiler compiles itself and the kernel with $LK,"BootHDIns",A="MN:BootHDIns"$(). The secondary metric is how understandable the code is. The $LK,"ZealC",A="FI:::/Doc/ZealC.DD"$ language should be changed to optimize these metrics, as Terry Davis did when he changed type casting from prefix to $LK+PU,"postfix",A="FF:::/Doc/ZealC.DD,postfix"$. * The primary metric for resolving all ZealOS code governance issues is how fast the compiler compiles itself and the kernel with $LK,"BootHDIns",A="MN:BootHDIns"$(). The secondary metric is how understandable the code is. The $LK,"ZealC",A="FI:::/Doc/ZealC.DD"$ language should be changed to optimize these metrics, as Terry Davis did when he changed type casting from prefix to $LK+PU,"postfix",A="FF:::/Doc/ZealC.DD,postfix"$.
@ -34,6 +34,8 @@ $FG,5$$WW,1$$TX+CX,"ZealOS Charter"$$FG$
* Documents are not for printing. They're dynamic, intended for the screen. * Documents are not for printing. They're dynamic, intended for the screen.
* Just one 8x8 fixed-width font. $FG,4$No Unicode, just Extended ASCII$FG$. Other countries can make their own versions. The versions should be just for one language and platform. * Just one 8x8 fixed-width font. $FG,4$No Unicode, just Extended ASCII$FG$. Other countries can make their own versions. The versions should be just for one language and platform.
* Fully self-hosted self-reproducing functionality on bare-metal and in VMs, primarily via AHCI ATAPI burned CD/DVD discs (ñR/W).
$FG,8$ $FG,8$
* "Commodore 64" is a trademark owned by Polabe Holding NV. * "Commodore 64" is a trademark owned by Polabe Holding NV.
* "Windows" is a trademark owned by MicroSoft Corp. * "Windows" is a trademark owned by MicroSoft Corp.

25
src/Home/Roadmap.DD
View file

@ -1,25 +0,0 @@
$WW$$FG,5$$TX+CX,"Project Roadmap"$$FG$
The goal is to be a fully-functional, self-reproducing x86_64 PC operating system running in $FG,2$ring-0 only$FG$, designed for modern machines with $FG,2$AHCI$FG$.
Roadmap:
- AHCI driver that is capable of reading and burning CD/DVD discs (ñR/W).
- Write drivers for the 5 most common ethernet cards.
- PCNet-II (Virtualbox)
- 82545EM (VMWare; QEMU?)
- ...
- ...
- ...
- Create a clean and robust networking stack that supports sockets, TCP, UDP, IP, ICMP, DHCP, and an HTTP library.
- Write applications using this networking stack.
- Write a JSON library, so REST APIs can be used.
- Whole system VCS, with root being top-level directory. Stored repo inside the OS, you can checkout any commit onto another partition and boot it to see what the OS was like in that commit.
- Pull updates directly onto root filesystem from network. (it's a repo source tree after all).
- Code clean up and refactoring.
- Perhaps support for USB keyboard and mice.