I DID IT! After a mad, possessed, sleepless 30 hour bender I finally solved the #programming language design problem I've been wrestling with for a decade! How to make a concatenative language both type-safe and infix/postifx (not RPN). I think this is the most elegant language I've ever designed: https://gist.github.com/Kroc/62fd60dda68f667e0e4d94c9e08bf2af #pling #ezOS

Anyway, the important take-away is that the OS and the programming language are essentially one and the same. Any library or app can be reassembled on demand if a binary copy doesn’t exist. Clearing the cache of assembled binaries would lead to everything being reassembled to deal with major code changes. #ezOS

In #forth when you want to call an external function you include (execute!) the external file which assembles the functions into memory and adds the name entries to the “dictionary” so that they can be found. It builds a monolithic binary at run-time! I want to avoid having to assemble the external functions every time you want to run a program so I would separate the dictionary so function names can be linked at assembly without yet loading the code before execution. #ezOS

That is, where as a #Forth program is a script that assembles the program into memory at runtime, I want to go with a more direct ‘list of instructions’ that can be quickly assembled into an equivalent (and reversible) compact binary form that can be executed. BTW I’m calling this OS concept #ezOS