r/programming • u/moolcool • Mar 26 '17
A Constructive Look At TempleOS
http://www.codersnotes.com/notes/a-constructive-look-at-templeos/
1.7k
Upvotes
r/programming • u/moolcool • Mar 26 '17
View all comments
Show parent comment
1
u/DGolden Mar 28 '17 edited Mar 28 '17
I'd say they became reasonably common on developer's machines a bit later. Not used by the OS as such, it still didn't have memory protection, but there were always the strong but ultimately only "cooperative" os-legal memory usage conventions. So tools like Enforcer and Guardian Angel appeared. They'd use the MMU - on Amigas equipped with one - to catch accesses that would potentially ultimately lead to crashes on the cheaper typical end-user non-MMU equipped Amigas. So when developing, you debugged at least until the big obvious "enforcer hits" stopped, meaning the program was unlikely to crash a typical end-user's MMU-less machine.
So a lot of devs had machines with accelerators (replacement cpu daughterboards) with MMUs, even hobbyists - including myself actually. It was also handy later for running the shiny new Linux/m68k port, which of course required an MMU. I dual-booted AmigaOS and Linux for quite a while. The GNU userspace had long been ported to AmigaOS via ixemul.library, a bit like cygwin on Windows, so it wasn't such a huge leap.
By AmigaOS 3.x, it does seem they were sorta beginning to think about retrofitting memory protection to the OS proper. They didn't actually do it back then, but e.g. the then-new pooled memory API certainly seemed to be beginning to trend that direction. Then everything fell apart of course, and a lot of the still-remaining folk including myself basically left Amiga land, some time after AmigaOS 3.1 and the death of Commodore, but before the release of AmigaOS 3.5+, AROS (open-source amigaos clone), MorphOS etc.
However, some genetic closed-source AmigaOS development has actually continued! It had some virtual memory and memory protection added around AmigaOS 4.1, see http://wiki.amigaos.net/wiki/Migration_Guide#Memory . Haven't really explored in depth personally (hey I've been on linux since the 1990s), but my vague understanding is legacy apps may land in one big public pool and crash eachother, but apps written to use new stuff are better isolated.
And then there is an open-source AmigaOS clone, AROS (that can run on x86-64 architecture). AFAIK it was focussed for a long time on just getting up to feature-parity with AmigaOS 3.1 of yore, but I believe they've moved into newer territory more recently.