🚀 go-pugleaf

In article <48041@ogicse.ogi.edu> francis@ese.ogi.edu (Francis Moraes) writes:

   sdk@med.ge.com writes:

   >After reading IBM literature, talking with one individual and
   >thinking about the postings here I decided that I should post
   >several questions and study the responses before making any
   >purchases.
   >
   >1.  If you value the ability to multi task as a driver to use
   >    OS/2, how much to you **really** multitask ?

Most people think, that multi-tasking is only a matter
of two distinct processes running asynchronous.
But, what is often forgotten, you can multitask or
better multithread IN an application.
For a fast processor, it makes not much sense
only quering a mouse and routing a message queue.
Other useful things can be done in the meantime.
Look at CorelDraw: While you`re choosing objects,
CorelDraw connects them internally.
Then, if you really want them to be connected, the
work is already done.

I can imagine much more things, where multithreading can be used.
Sorting while the user enters data in a database,
Saving, while an appl. prints to the spooler, etc.

But here is an example out of life:
One day, I was trying to connect to a local BBS.
Not to say, that the BBS was always busy...
Instead of waiting for the connect, I was installing 
a DOS-Game on my FAT-Partition, and between disk-changes,
I played another game.

The BBS was still busy, so I started Emacs,
loaded my current C-Projekt, made a few changes
and compiled it via Emacs.
Emacs started the make-process parallel, so I could
change the documentation while compiling.

That really saves time !
I will never go back to a non-multitasking (or "kooperative Multitasking)
OS. 


Greetings, :)ochen