> that coupling became the downfall when the computer hardware moved faster than Amiga software could be brought along.
Both hardware and software moved ahead while Commodore invested in the wrong things. Amiga was late to adopt VGA monitors and PCs quickly surpassed its capabilities. When I mentioned porting AmigaDOS and Intuition to 2/386's, it would be to keep the OS compatible at the C source level as much as possible, with workarounds for hardware when it's different, but always at OS API level so that non-game software (or non-Amiga-like games) could be ported from source.
I don't think it'd have saved Commodore or the Amiga (I think the Sun deal, where Sun would sell 3000/UX boxes was a better bet for that, or maybe not ditching the CBM 900 but, instead, building Amiga with Coherent instead of AmigaDOS).
I don't think most of it was originally implemented in C.
> at OS API level
That's the problem. Keep the original non-protected-memory APIs and you can't have memory protection; add memory protection, and it can't be API-compatible.
Both hardware and software moved ahead while Commodore invested in the wrong things. Amiga was late to adopt VGA monitors and PCs quickly surpassed its capabilities. When I mentioned porting AmigaDOS and Intuition to 2/386's, it would be to keep the OS compatible at the C source level as much as possible, with workarounds for hardware when it's different, but always at OS API level so that non-game software (or non-Amiga-like games) could be ported from source.
I don't think it'd have saved Commodore or the Amiga (I think the Sun deal, where Sun would sell 3000/UX boxes was a better bet for that, or maybe not ditching the CBM 900 but, instead, building Amiga with Coherent instead of AmigaDOS).
Anyway, it'd have been fun.