@z3bra, @ninjacharlie:
There are of course also https://www.github.com/andrewchambers/c, git.suckless.org/scc
and https://www.github.com/rui314/8cc.
I would love to use one of these, but tcc for example does not produce symbols for gdb
and can't be used with musl.
But I would rather try to improve an existing C compiler/standard library that
does not suck instead of making a new one. I mean, pcc, tcc, 8cc, scc and c are
already enough compilers for this world. And there are also enough C standard
library implementations (muslibc, ulibc, and dietlibc). Just getting one of
these working with one of the others would be a huge step forward. Writing a new C compiler
is not the answer (imho).
The same is true for lisp interpreters, text editors and kernels: in another thread I already mentioned
tinyscheme, which is a quite beautiful scheme implementation in ~5000 lines of C, it is complete,
stable and all of that. Because of this I don't see any reason to develop yet another lisp
interpreter which is a little bit different from a good, bug-free and existing one.
If you are searching for a scriptable vi-compatible editor, there is for example [vis](https://www.github.com/martanne/vis). Yes, I know, the scripting is in lua, but I am also sure that there is an existing vi
with lisp integration as well.
I don't see what is so bad about minix either. To me, it seems like minix is a quite nice microkernel
in ~12000 lines of code, with more than 20 years of constant development.

Of course, nih is a trap I fall into myself a lot of times.
I mean, on my ideas list, there are 7 ideas for new programming language implementations.
Because I know this is not a good thing, I decided to put forks and contributions to other
projects first. I research if there is an implementation of what I want to write, and if
it adheres my standards of code. If it does, I throw away my plan, and try to write things
I consider fun or important (whatever).

-------END OF RANT

I hope this was not too rude.
If it was, ignore it.