uncharted wrote:
downix wrote:
@uncharted
Huh? Where the heck are you getting this stuff on the OS's design? BOTH OS's are using a sandbox technique here. The only difference is that one seperates the new MP-enabled kernel from the old non-MP kernel. This way, should a non-MP app kill itself, you don't loose the entire system, just the non-MP protected section.
The OS 4 feature list it explains that it does not use a Sandbox approach. I mean before you started slagging it off you did actually READ the information available on it didn't you?
I read Ben Hermans latest statements on AOS4, and he said clearly that to seperate new-API from old-API they will be using a sandbox.
And, yes, I have read the AOS4 feature list. I dissected it quite completely, and it meshes with what Mr. Hermans said, a sandbox is needed for future roles.
So you are saying that I can write an application for MOS that makes use of all the advanced features of Quark including MP?
That's either great news or total rubbish.
Nope, but you can't make an application that can use all of the advanced features of ExecSG either. So no difference here.
-EDIT-
And MOS has VM.
Available to the applications written for ABox?
Yes. However, like in QNX, with MOS the VM is added using a system module, so apps can only make use of VM if they are designed to.
Having run such a system with QNX, I know very well how nice that is, not having the OS decide when to allocate VM but instead the app decide on exactly how much VM it needs. Gives me far more control over the applications that way.
-edit-
Got some clarification about MOS's VM system. It is currently in internal beta, but not a high priority for inclusion into the public release.