I don't? Read through this thread again and you will see that I have responded to the comments of various people. Without resorting to ad hominem attacks as you are doing now. I've made this point before, but again: yes you can add extra bits to AROS to get a semi-usable system. That doesn't make it a usable system. Someone could get a bare CPU and add various bits to it to make it a usable system, that doesn't make it a usable system in its own right. You have to download extra bits to make it equivalent to something that already works fine out of the box. What good is that?
Also with AROS x86 you can't even do that; if a piece of software is not available in an AROS x86 version you can't use it at all. Unless they finally have working 68K emulation, which they didn't last time I checked. And like I and others have said before, there's no reason for any 68K user to bother with AROS: it's slow, missing features and ugly. Really, it has next to nothing to recommend it except for copyright issues, which seemed to be the main reason Toni Wilen was bothering with it, because it could be distributed freely with WinUAE, not because it was actually better. The same applies to various BIOS replacements that are included with various emulators. For best compatibility you use an authentic BIOS which, by definition, is 100% byte-for-byte identical. Substitute BIOSes are included for legal reasons only, generally the first thing one does is get an authentic ROM dump.
The main one is that they aren't palette independent. So users have to keep the default colours; if the user changes their palette all their old-style icons will look awful. And if the developer used a non-standard palette to begin with, you have to match your palette to theirs. Not everyone runs MagicWB. MagicWB doesn't even define more than 8 colours IIRC. The original icon format was designed for OS1.x which didn't support deep screens. Even if you assume that neither the developer nor the user has modified the colours from the default, you still can't guarantee what palette is in use. Eg. 1.x has a different default palette as compared to 2.x.
You install a distribution (OS3.5/3.9) and then compare it to a backbone that is aiming to reimplement 3.1. API and not suited for users and then make your judgements? I have shown you screenshots of 68k software running on it no reaction from you.
AmigaOS is not in development anymore, 3.9 was the last update and then there will be no updates in future. 4.X is another branch for me because it needs completely different hardware. So if anyone wants development then there is only one potential chance.
And to make some comments about what you wrote about X86... there IS a working emulation in AROS but only in certain distributions (Icaros Desktop and Aeros), not in nightly builds. They are for testing for developers not users. 68k emulation runs in a kind of box with UAE, integrated but not the same as on MorphOS or AmigaOS. I do not know when you last checked it but it seems to be very long ago or you have just looked at a nightly build (that has no 68k emulation integrated).
"no reason for any 68K user to bother with AROS: it's slow, missing features and ugly."
Really? Who has said that before? It is slow? Where and when? On real hardware yes, that was this discussion about, on emulation (what certainly most use today) no. Missing features? Which? I work for a couple of years on my distribution that is based on Aros 68k, which features are missing? As I explained before distributions are for users (not nightly builds). Ugly? Really? How that? Show me a example of that? I have a nice RTG 24bit background from Wawa, use Magellan as Desktop Manager and support almost any GUI technology inside that was ever available.