Path: utzoo!utgpu!watmath!iuvax!rutgers!cbmvax!daveh
From: daveh@cbmvax.UUCP (Dave Haynie)
Newsgroups: comp.sys.atari.st
Subject: Re: Multitasking on the ST
Message-ID: <7596@cbmvax.UUCP>
Date: 9 Aug 89 17:44:41 GMT
References: <89080709104987@masnet.uucp>
Organization: Commodore Technology, West Chester, PA
Lines: 36

in article <89080709104987@masnet.uucp>, david.megginson@canremote.uucp (DAVID MEGGINSON) says:

> The advantage of multi-tasking is that every program would not have to
> try to emulate every other program (note the plethora of programs with
> file functions like copy and disk format built-into them), and that
> different sorts of programs would not have to compete with each other,
> but could come together into some kind of large, useful whole.

That is basically what AREXX on the Amiga does for non-trivial cases. 
Certainly a single-tasking wordprocessor can include a minimal database
function, or allow small specially written programs (Desk Accessories) to
be called up for other peripheral functions during an editing session.

But if a particular operation is needed often enough in the wordprocessor,
it should be easily added to that word processor.  You're not going to be 
able to convince the author of your favorite program, in most cases, to add
in this feature that you use constantly unless it's likely to be needed by
lots of users.  

Now move this to a multitasking system like the Amiga.  The wordprocessor
has only wordprocessor functions in it, and one extra goodie, an AREXX port.
If I find I need a database function from within my wordprocessor on a 
regular basis, I can write a simple AREXX macro that'll use the real, full
fledged database program, via it's AREXX port, from within my wordprocessor.
All pretty transparent once the macro is written, as one might expect.

Multitasking has been around for quite some time.  It's really only now 
becoming extremely useful, rather than just handy, to users, thanks to user
interfaces which make it far easier to manage separate tasks that UNIX-like
job control, and thanks to inter-process communication mechanisms like
AREXX, which let any program become a system resource that all other programs
can take advantage of.
-- 
Dave Haynie Commodore-Amiga (Systems Engineering) "The Crew That Never Rests"
   {uunet|pyramid|rutgers}!cbmvax!daveh      PLINK: D-DAVE H     BIX: hazy
           Be careful what you wish for -- you just might get it