MorphOS Developer
Posts: 586 from 2003/2/24
From: finland, the l...
Quote:
Quark *is* MorphOS so it wouldn't be MorphOS at all if you didn't have Quark. If the ABox ran on any old host OS then it wouldn't be any different from AROS in system architecture.
Not quite, ABOX is actually AmigaOS 3.x binary compatible, while AROS isn't. MorphOS provides 68k compatibility, while even if you compile AROS for 68k it won't be (fully) binary compatible. AROS is aiming to have some level of 68k compatibility through UAE, but this will never provide same level of integration as direct 68k compatibility provided by MorphOS. MorphOS maintains backward compatibility, while AROS doesn't (or at least hasn't so far in many cases). So it would still be quite different from AROS. AROS might be moving more towards MorphOS however (but if this ever happens to full extent remains to be seen).
Quote:From MorphOS: The Lightning OS it states:
Quote:
Although a functional clone of the AmigaOS is a nice experiment, the real potential for MorphOS is found in its ability to provide for more advanced OS features not found in the AmigaOS. This is possible because MorphOS is built around a very flexible, powerful, and compact microkernel called Quark, whose structure is totally unrelated and independent from the Amiga and Linux kernels.
This is some sort of conclusion by the writer of the article, not by the MorphOS Team. Most of the MorphOS features are possible regardless of Quark. Quark provides some very basic low level services for Abox, that's it pretty much it. You could well replace Quark with something else and MorphOS would still appear and function the same as before.
Yes, I am aware that the article was checked by Frank Mariak, but still that section doesn't make much sense. IMHO it should have been corrected or at least formulated differently. As it is now, it gives the impression that these things are ONLY possible because of the Quark, and this is not the case.
Quote:
But why not let others try and take Quark forward by providing an API or dev information or something concrete so that Quark can be explored?
I've already explained that you can't do anything really usable with the Quark as it is today. No documentation will change that.
Quote:
Perhaps Quark is planned to be phased out in the longer term?
It isn't. It does its job very well.
Initially Quark was supposed to get more important role than it ended up with. I think this topic can be laid to rest now.
[ Edited by Piru on 2009/4/21 10:01 ]