Order of the Butterfly
Posts: 301 from 2003/2/24
From: Genesi
@CISC
MorphOS does not need to retain compatibility. Do you want to know what Freescale did when we told them we had an OS that had m68k compatibility on the Pegasos?
They laughed. It's an absolutely pointless feature. Apple shipped MacOS X with a "MacOS 9 in a window" emulation rather than drag m68k emulation to X. They shipped OS X for Intel with Rosetta.. but that is far, far gone now (check out the stuff for Snow Leopard, they say it's 7GB smaller - that's 7GB of PowerPC fat binaries and compatibility layers and emulation cut down to only support 64-bit Intel systems)
Whatever chip MorphOS runs on, it should be one where MorphOS can become more than an Amiga Workbench clone that runs applications which stopped being compiled 10 years ago. I can't think of a single component - besides translator.library/narrator.device and ARexx, the latter of which I recall is your project - which may still require something being emulated on the m68k. The whole m68k emulation thing also adds a tremendous overhead on the API.
I've been involved with a couple Amiga-clone OS projects over the years and by far the best one was Carsten Schlote's CaOS project at Met@box. The thing was damn sweet; take AmigaOS and take out all those functions that did things the old way, and just do them the new way. No SetPatch+NewSetPatch+NewNewSetPatch+whatever, just one function that does it. You clean up the API and everything works so much better.
Ditch all the Amiga Blitter assumptions and interleaved bitmap support out of the Graphics API. Throw away the 50Hz power supply clock! Actually implement real multi-user support and memory protection.. rework the input APIs and support Unicode across the entire system without weird hacks. Bundle a web browser class as standard. Stop being an emulation "box" and start being an operating system.
A lot of those concepts got dragged into MorphOS by Stefan Stuntz for MUI 4 (which got rid of a bunch of libraries which caused some compatibility problems - amazing how many people used the "private" muigfx.library :)
Maintaining compatibility is bloat, and if you market MorphOS outside of the <500 people who really want an Amiga clone through rabid zealotry, it is not required. MorphOS has an opportunity to become a top quality embedded operating system with a significant market share, but it will never be this way if you follow the Amiga development model and maintain binary compatibility.
If MorphOS doesn't want to go in this direction, then I guess you will eventually stop getting registrations and bounties and everyone that matters will move to AROS, because for a community-written open source and "libre" project, they have a much better business model.
Nonetheless, I wish you luck with your diminishing market.
Matt Sealey, Genesi USA, Inc.
Developer Relations
Product Development Analyst