diff options
| author | Taylan Kammer <taylan.kammer@gmail.com> | 2025-03-29 23:56:22 +0100 |
|---|---|---|
| committer | Taylan Kammer <taylan.kammer@gmail.com> | 2025-03-29 23:56:22 +0100 |
| commit | d6e50e7a631d0dfe8d41438be89f8b00dfc9a4df (patch) | |
| tree | 741717b08aafac370ce416f901c4698c62b39bfa /notes/boot.md | |
| parent | fc23b42c6e2183c8ca8b6c42dc4e90d8061f835d (diff) | |
add some unfinished notes and docs
Diffstat (limited to 'notes/boot.md')
| -rw-r--r-- | notes/boot.md | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/notes/boot.md b/notes/boot.md new file mode 100644 index 0000000..758d264 --- /dev/null +++ b/notes/boot.md @@ -0,0 +1,17 @@ +# Bootstrapping Zisp + +In my opinion, any serious programming language must have a serious +bootstrapping strategy that addresses the "Trusting Trust" issue aka +the Thompson Hack. The easiest way to do that is making sure that +your language can be bootstrapped from an existing language, which +itself has some solution to the problem. + +Currently, I'm thinking of implementing Zisp in Zig. (That's not the +entire reason Zisp is called Zisp, and I might choose a different +language eventually, and/or rename Zisp, but anyway.) + +Zig, in turn, will *hopefully* be possible to bootstrap from C in the +future, or some language implemented in C. For C, there are some ways +to bootstrap it from scratch. + +*** WIP *** |
