Dave Needle on Amiga...

[psxphill]

WE could run multiple instance of a program and only have ONE copy of it in memory with multiple user/data areas.

The Amiga could do this too.
 

Even without memory protection, our program were structured better and were always written for position independent addressing.

Amiga software was position independent.
 
You can't really blame the OS for buggy software, that is down to the programmers that use it. If I released a ton of buggy OS-9 apps then would you change your opinion of the OS? Of course not.

[psxphill]

So Moron? well if he is ,i hope there are another ten thousand like him Brian

I hope not, the only other positive statement I've heard about him are that some people find his trolling and thread derailling hilarious.
 
I don't care that he posted a youtube comment though.
 

And the OS doesn't manage this function leaving the task to "friendly" applications.

The OS manages sharing executables but with no MMU you are reliant on "friendly" applications. You could just as easily write an OS9 application that uses self modifying code.
 

And most code on 68K and later machines is position independent (or at least position relative).

I'm not sure what you're getting at there. The operating system in machines without MMU's relocate their executables at load time, which AmigaOS does too.
 
You're still saying the OS is bad because of programmers that wrote applications, those same programmers could write OS-9 applications.

[psxphill]

In any case, it was not a common function of Amiga programs.

That is irrelevant, you're blaming the OS for bad software.

[psxphill]

It was required.

How could the OS detect or enforce it? Did you just run into problems if you ran more than one copy?

[psxphill]

No, it is a required function.

Required by who and how was that requirement tested for and enforced?

[psxphill]

Until I'd mention that the OS had several module classes, it would have been hard to explain while modular reentrant code was an advantage.
Plus you have the ability to load and unload module dynamically (and I

So do all versions of AmigaOS & libraries and devices are "required" to be re-entrant on AmigaOS (*). You can't unload code while it's in use though, I don't know if OS-9 can do that.
 
Later (Kickstart 1.3 IIRC) they added the option of also marking applications as re-entrant so the code can be shared for those too. Again you could preload or unload them.
 
(*) You could use a semaphore internally to serialise access to certain parts of the code, which you'd want to do if the library/device talk to a resource that can only satisfy one request at a time & this technique could also be used if you wanted to do something strange like self modifying code as well.
 

You guys need to look at how a microkernel based OS is designed to work. It encourages specific programing habits.

AmigaOS is microkernel, what makes you think it isn't?