...one starts to have a clue how to program an OS?
OK, so I am a n00b. I went through the 600 page "gentle introduction" book, finished the vending machine simulator. So I could code a vending app now, but I don't really need one, Ebay is already invented. So I asked myself, "what I'd like to use this LISP knowledge for now"? Of top top of my head, only two uses hit me.
The first, writing a program to predict financial markets to make myself a kajillionaire would be a non-sequitur. What is there I couldn't predict already? The markets will keep going down, with the Fed announcing nebulous imaginary gain statistics. Do I need a program to tell me this? No. Chart the exact amount fibbed? 1% more than the last time. Done, still didn't need a program.
OK, let's try idea #2. How about writing an OS that doesn't suc... erm, vacuum attract? Like, an universal OS that would run on any bit-depth processors because before slinging the first bunch of bits anywhere, the OS would spend a couple of microseconds to determine (compare with yesterday's saved result) how many bits the processor uses and at what speed, and work from there. Same deal with all devices / peripherials / programs (as long as the CPU bit depth > program bit depth) so adios "drivers" and the need to update to a new OS just because new faster hardware. Learn the OS once, use it 40 years later on 1 million times faster machines. Running the same 40-year old program, if you want. Bill Gates would so hate me.
Except... having read the first book, I still have no clue how to start coding this idea #2. So realistically, how many more LISP books it will take before the fog starts to lift off? Thank you for all helpful insight.