Author: Virgil Dupras <email@example.com>
Date: Sat, 25 Jun 2022 08:44:47 -0400
Clarify "Why build this OS?" in README
1 file changed, 8 insertions(+), 4 deletions(-)
diff --git a/README.md b/README.md
@@ -51,12 +51,16 @@ possible to elegantly marry it with languages that like complexity better.
This mix, we believe, could provide a creative user with computing powers rarely
seen with other approaches. We've got to try it.
+To be clear: this is a research project, we don't know what it will yield
+beforehand. We have the intuition that it might lead to a big "ah ah!" moment
+and reveal a breathtaking combination of power and simplicity.
## A whole OS built from source on boot
One thing that makes Dusk OS special is that it boots from a very tiny core
-(less than 900 lines of x86 assembly). From this tiny core, on boot, it builds
-its way up to a system that has a functional C compiler, which then allows it
-to bootstrap itself some more.
+(900 lines of x86 assembly). From this tiny core, on boot, it builds its way up
+to a system that has a functional C compiler, which then allows it to bootstrap
+itself some more.
With regards to "source bootstrapping", it's even more extreme than Collapse OS
because modern machines allows this process to run very fast and the whole
@@ -90,7 +94,7 @@ Here's the plan so far:
Currently working on step 2 of the roadmap. The C compiler has a fair chunk of
the language implemented already. You can see a sample of what it compiles in
-`fs/tests/cc/test.c`. It technical documentation is at `fs/doc/cc.txt`. What's
+`fs/tests/cc/test.c`. Its technical documentation is at `fs/doc/cc.txt`. What's
missing currently is:
* ops width depending on type (everything is dword)