> Yes, it certainly would suppose a lot of coding, but I'd prefer waiting
> (I am used to it anyway as well as every Amiga user) and then having a
> stable proggy, than having a system that crashes 3-10 times per day. And
> for now it is sure that MUI is the bad guy, because I have spent a lot
> of time trying to remove possible hacks and stuff that is not needed.
> It's always MUI programs that crash.
This is not a logical argument. Because you have had MUI programs
crash on you before, you assume that its MUI's fault, simply because
the programs that crashed used it.
My system usually has several days uptime in a row. I'm *mainly*
running MUI apps. If I have a crash, its because of some beta
software. My fault for running it, I'm testing it so you lot
(hopefully) don't have to crash. On a normal day I'll have 2+ AmIRCs,
2+ Voyager3's, Microdot II (currently with 52,000 messages in the
database), STRICQ, Daywatch, approx 10,000 hacks (actual number may
vary :)), and DOpus Magellan.
If you're crashing 3-10 times per day, maybe its about time you give
your system a birthday and start again. There's something *seriously*
wrong with your system. It's not MUI.
> And after many many years, MUI is not even processor optimized. I've got
> a 040 but many times it seems just like a 000 here.
>
> Sad but true.
Amiga processors are shitslow anyway. It's like designing shoes that
will allow a turtle to move a bit faster - still slow.
It has been repeatedly said that so-called "optimisation" of MUI for
other CPUs wouldn't actually do much.
Jason
--
Jason Murray
Webmaster, www.vapor.com
[EMAIL PROTECTED]
__________________________________________________________
AmIRC Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
