Yes, that's the plan, having full view DSL features. The issues are GPU drivers, as you don't get any specs from the manufacturers, so it will either be a software renderer or using a VGA/SVGA backend.
An exoKernel/paraKernel is only securely multiplexing the resources. Everything happens in user-space (memory allocations, scheduling, etc.), so you can theoretically run every app from every OS at the same time (if you provide a libOS being able to handle the API calls of the specific OS). You would be able to run only one single app or multiple ones. The OS is just another application so you can boot into an OS or an application itself, running on bare-metal.
I totally agree with your post. The issue with lacking drivers are often lacking specs (mostly for GPUs) so its not always the fault of the developer/project.
I'm contributing code to Red myself and actually working on a PoC Kernel/OS implemented in Red/System. Its architecture will be an exoKernel/paraKernel. You would be able to directly boot into your IDE or app just like in the good old C64/Amiga (Game mode) days.
What I really want to have is running Red/OS on the Mill CPU.
Yes, that's the plan, having full view DSL features. The issues are GPU drivers, as you don't get any specs from the manufacturers, so it will either be a software renderer or using a VGA/SVGA backend. An exoKernel/paraKernel is only securely multiplexing the resources. Everything happens in user-space (memory allocations, scheduling, etc.), so you can theoretically run every app from every OS at the same time (if you provide a libOS being able to handle the API calls of the specific OS). You would be able to run only one single app or multiple ones. The OS is just another application so you can boot into an OS or an application itself, running on bare-metal.