3 ms·
Funny thing is, my old OS project [1] is more or less that - it could be a typical OS with separate tasks and so on, but it is effectively a single program, and
by Artlav 9y ago
Funny thing is, my old OS project [1] is more or less that - it could be a typical OS with separate tasks and so on, but it is effectively a single program, and can easily be compiled as a single program with all the standard calls replaced with OS-level implementations.
In practice, these are two different sets of use cases - in one you want clean abstractions, process separation, storing message passing and so on, in the other you want to get the call from your code into the libservice ASAP. Trying to (unwittingly) combine the two gave me quite a bit of grief.
Another disadvantage is a lack of any protection (at least in my implementation), since everything shares the address space.
Anyway, it's odd to see that a random idea i had 17 years ago is actually starting to get used.
[1] http://orbides.org/aprom.php http://orbides.org/aprom.php
- beefhash 9y agoIsn't that basically what SQLOS is doing for Microsoft SQL Server[1]? [1] cf. https://blogs.msdn.microsoft.com/sqlosteam/2010/06/23/sqlos-resources/ https://blogs.msdn.microsoft.com/sqlosteam/2010/06/23/sqlos-...
- rwmj 9y agoYours sounds like a Language-based Operating System, except you didn't implement protection in the language. Anyway they've been around for a very long time. The Burroughs system that I'm familiar with was around in the 1960s (from 1961 according to Wikipedia). https://en.wikipedia.org/wiki/Language-based_system https://en.wikipedia.org/wiki/Language-based_system