> Because I want to follow my vision. There is space for more than one thing in the world. That's nice... but I think you're underestimating the amount of work

> Because I want to follow my vision. There is space for more than one thing in the world. That's nice... but I think you're underestimating the amount of work to produce something you actually want to use: > Yeah, that's my plan for the weekend. I'm currently working on a minimal Lisp implementation written in Rust, > One of the questions I want to answer is what is the minimum amount of constructs you need to have complete control over your hardware, while able to rewrite the entire kernel at run time. I bet it's not that many. You should take a look at both PreScheme (part of Scheme48) and Squeak. There's a lot of prior art you can look at without compromising your vision. I'd also suggest you commit to a (modest) end state you want to achieve. I'm reminded that Linus Torvald's original motivation for Linux was to understand the multitasking hardware in the 80386. His first working development "kernel" ran two fixed tasks that printed something like A's and B's. So you may be well served by starting with something minimal, but functional and building out as you have time. This also has the advantage that if you run out of steam for the work, you'll still be able to explicitly state you achieved an interesting goal. (As opposed to "Yeah, I started out building a bare metal Lisp, but got bogged down in the interereter and...")