<aname="l13"></a>and is designed to do the same things a C64 did. This saves and order of magnitude complexity. For example, the </span><ahref="https://zeal-operating-system.github.io/ZealOS/Doc/RedSea.DD.html#l1"><spanclass=cF4>RedSea</span></a><spanclass=cF0> file
<aname="l19"></a>bases for each machine's custom hardware. There is one graphics driver instead of 50 for different GPUs. This saves an order
<aname="l20"></a>of magnitude complexity and makes for a delightful API, so developer's code is not like a frayed rope end.
<aname="l21"></a>
<aname="l22"></a>
<aname="l23"></a>
<aname="l24"></a>* Everything runs in kernel, </span><spanclass=cF2>ring 0</span><spanclass=cF0>, mode.
<aname="l25"></a>
<aname="l26"></a>* </span><spanclass=cF2>One memory map</span><spanclass=cF0> for all tasks on all cores with virtual addresses set equal to physical, just as though paging is not used.
<aname="l27"></a>
<aname="l28"></a>* One platform -- </span><ahref="http://en.wikipedia.org/wiki/Amd64#AMD64"><spanclass=cF4>x86_64</span></a><spanclass=cF0> PC's, no 32-bit support.
<aname="l32"></a>* Least (greatest) common denominator hardware support. Mostly, one driver for each device class. We can't be in the
<aname="l33"></a>business of different drivers. Compatibility is the greatest challenge for PC operating systems. Disk code does not use
<aname="l34"></a>interrupts, avoiding compatibility risks. </span><spanclass=cF2>PS/2</span><spanclass=cF0> keyboard/mouse is used instead of </span><spanclass=cF2>USB</span><spanclass=cF0>, also more compatible.
<aname="l36"></a>* Updates whole screen at </span><spanclass=cF2>60 fps</span><spanclass=cF0>, optimized for full screen games where </span><spanclass=cF2>InvalidRectangle</span><spanclass=cF0>s are counter-productive.
<aname="l37"></a>
<aname="l38"></a>* One font, 8x8. Text and graphic layers done in software with text normally on an 8x8 grid.
<aname="l39"></a>
<aname="l40"></a>* Compiler extends all values to 64-bit when fetched and does only 64-bit computations intermediately. Assembler has minimal
<aname="l41"></a>16-bit support, good enough for compiling boot loaders.
<aname="l47"></a>* </span><ahref="https://zeal-operating-system.github.io/ZealOS/Doc/CosmiC.DD.html#l1"><spanclass=cF4>One language</span></a><spanclass=cF0> and compiler for command-line, scripts, songs, automations and code.
<aname="l53"></a>* No distinction between </span><spanclass=cF2>thread</span><spanclass=cF0>, </span><spanclass=cF2>process</span><spanclass=cF0> or </span><spanclass=cF2>task</span><spanclass=cF0>.
<aname="l55"></a>* The </span><ahref="https://zeal-operating-system.github.io/ZealOS/Kernel/Sched.CC.html#l1"><spanclass=cF4>Scheduler</span></a><spanclass=cF0> is for home systems. It is not preemptiove. Disk requests are not broken-up, so sharing is bad. It's
<aname="l63"></a>* All tasks have a heap and a sym table. Scope is that of environment vars in other operating systems. As text is typed at
<aname="l64"></a>the command line or you run programs by </span><spanclass=cF2>#include</span><spanclass=cF0>ing them, the syms go in the table. If a sym is not found, the parent task's
<aname="l65"></a>table is checked. The father of all tasks has the API syms you'll need waiting in it's table. No need to </span><spanclass=cF2>#include</span><spanclass=cF0> headers.
<aname="l67"></a>* No need for namespaces -- scoping occurs automatically based on task symbol table hierarchy with the </span><ahref="https://zeal-operating-system.github.io/ZealOS/Doc/Glossary.DD.html#l154"><spanclass=cF4>System Task</span></a><spanclass=cF0>'s symbol
<aname="l70"></a>* Sometimes, we </span><ahref="https://zeal-operating-system.github.io/ZealOS/Doc/CutCorners.DD.html#l1"><spanclass=cF4>cut corners</span></a><spanclass=cF0> in the interest of keeping the code beautiful.
