Hello eekee,
Yes, I can see you are a Forth fan, good to greet you and thank you for your feedback. Ok, a little background around the motivation of C to forth, simple’s way to put it is, there are more C programmers than Forth programmers.
However, looking at this form another prism, if you follow my concept to it’s most extreme potential, you would be looking at an OS that could be the basis for a massive parallel application platform, where each application includes a subset of the forth kernel… and you potentially can have thousands of applications running all at a very small footprint. You would need a C interface or otherwise to build these apps, and they can be sort of like Lambda functions in their simplest forms… if there would be any chance at getting any adoption, I would need to target a broader developer base than Forth. Makes sense?
Think of it as dockers yet that infrastructure to run most of it would be like 10/20 megabytes at the os level and about a meg each little kernel. It’s paravirtualization at its most simplistic form. Currently I have only considered share nothing. But threads can be a better reality.
It’s kind of like that movie, if you build it they will come… I can build the greatest App arena, but If I can’t find developer, then I will not see a single tenant in that arena…
Now, I’m no where near building a functional OS yet, I have the foundations to create loops dedicated to a single core and working on a binary format for the application, using simple UTF-8 rapers to build a compiled dictionary…
I would love feedback on the IPC for these little VMs.