@ Downix
While, yes, in theory someone could turn the ABox into a 100% native OS with some work, then you'd loose 90% of it's potency.
IMO compared to the currently provided solution, this would be preferable (Similar like PPCLinux is prefered by almost all Linux users over MkLinux usage). With hosting something like AROS or AmigaOS on top Linux or QNX the advantage of having many hardware drivers available to the host OS is obvious. However Quark does not offer these advantages.
It's an additional layer which negatively effects performance, this despite the good performance provided by solutions like MorphOS and Amithlon on modern hardware.
The only disadvantage I see is that Quark kernel features like memory protection, (features the ABOX environment itself does not really benefit from) could not be advertised anymore (marketing). But from the user point of view there wouldn't be any difference compared to the current solution. (usage)
My view regarding the benefits of a two kernel approach provided by various solutions:
- Amithlon => Many available Linux hardware drivers
- intent => Platform independence
- MorphOS => Marketing? (Could IMO backfire, if users discover that they cannot take advantage of the advertised features)