Re: [MiNT] XaAES / GEM memory issues

[Sven Karlsson <svenka@it.kth.se>]

Hi again,

> I see no difference to the traditional Unix/X11 system. Mouse & Keyboard
> are associated with the X11 server there.

The point is that if you look into how these systems are designed you
will find that they are quite different from the UNIX/X11 approach
although they provide memory protection, virtual memory and a windowing
system. However, they all privide a UNIX like programming interface in
some way. Now isn't that the entire point with MiNT?

If we really wanted "only" a UNIX/X11 system we would be much better off
running BSD, a sys V, or even Linux.

To summarise:

* NeXTSTEP is not a UNIX but there is a library that makes it BSD
compatible. It does not use X11 for windowing.
* BeOS is basically the same thing
* Plan9 knows about windows. Each window gets its own event queue
similar to a terminal. Again Plan9 is not UNIX but you can port UNIX
programs to it. In a way Plan9 is a successor to UNIX as it is written
by some of the most prominent people behind UNIX at AT&T.
* Well, I guess I shouldn't talk about NT at all but you can compile and
run UNIX programs on it although it certainly isn't a UNIX by far
although it is designed by several priminent UNIX people from Digital,
although it has borrowed more from VMS than UNIX.

Just because UNIX does one thing I don't see why MiNT should do exactly
the same thing in exactly the same way. MiNT is not a fullfledge
by-the-book UNIX and never will be as the TOS calls are there. If we do
it correct we can always keep the memory protection working.

If we really want to make a working AES with memory protection we need
an efficient design. I fear noone will use it if it is even marginally
slower than TOS' AES. Isn't the MagiC crowd's main argument that it is
faster?

Best regards
 Sven