Bill Cole at [EMAIL PROTECTED] said this on 9/20/01 8:07 PM
>There's a reason for this: while memory protection and pre-emptive
>multitasking are great for assuring stability and availability of all
>apps in a multi-processing environment, you can't beat an OS like
>Classic MacOS (or Novell, or DOS) for running one well-coded app
>really fast.
Agreed. It's harder to write an app for a non-pre-emptive environment...
takes more discipline and craft and knowing your app. With pre-emptive
OSes, programmers don't need to be as skilled or your input can vary more
without affecting code that's not been completely planned to the Nth
degree.
I had fun making The ZipBurst CGI VERY fast, but it can go faster still
as I go over the code. For 25 years I've had fun picking up other's
source code and making it go faster... easy to do when you have time to
sit back and study the code or take time to distance yourself from it and
come back. If the processor and I/O are fast, efficient and properly
threaded code can take advantage of them.
David
#############################################################
This message is sent to you because you are subscribed to
the mailing list <[EMAIL PROTECTED]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to <[EMAIL PROTECTED]>
