why? legacy code needs 68k emu anyway. uae/68k code may be treated as java of amiga world. one could push uea integration forward with some intelligent ideas. for instance perhaps it is possible to fire up only the 68k emulation and very necessary uae features first, on run of the 68k program to spare cpu power, then as soon as (and if at all) the program makes any call to amiga chipset features those could be dynamically thrown on in emulation.
apparently not an issue on aros anymore (waiting for confirmation), but may have to be improved, i still observe issues on 68k now and then, not knowing if they may be related.
at the point all three systems will want to go for those extended features that will likely set them on the same level of backward compatibility aros is now, namely uae. lets face it.
Interesting ideas.
I spoiled by MorphOS' excellent JIT software.
Only 68k code needs translation.
Operating system calls are executed natively (and are faster than running UAE).
If I need chipset emulation, then I go to UAE.
Although, with faster, multi-core processors this overhead would be less objectionable.
Of course, if we jettison backward compatibility, what will we have?