Path: utzoo!mnetor!uunet!husc6!mit-eddie!gary
From: gary@eddie.MIT.EDU (Gary Samad)
Newsgroups: comp.sys.amiga
Subject: Re: AREXX the low/medium level standard - NEXT THE HIGH LEVEL
Message-ID: <8762@eddie.MIT.EDU>
Date: 8 Apr 88 05:02:21 GMT
References: <8647@eddie.MIT.EDU> <893@nuchat.UUCP>
Reply-To: gary@eddie.MIT.EDU (Gary Samad)
Organization: MIT, EE/CS Computer Facilities, Cambridge, MA
Lines: 27

In article <893@nuchat.UUCP> peter@nuchat.UUCP (Peter da Silva) writes:
}
}Secondly, the HIGH-level IPC protocols for the machine already exist: namely
}files, pipes, and clipboards. Rather than create a whole new namespace, let's
}concentrate on tools to make that work better.

Files, pipes, and clipboards are simply not as powerful as a full IPC
protocall.  None of them allow CONTROL of an application.  They only allow
DATA transfer.

}Finally, as I said before... I'd go for REXX if there was a freely re-
}distributable dumb REXX server available. No, I'm not going to write
}one... I've got enough on my plate already.

Cmon.  REXX only costs 50 bucks.  And it's a real commercial product.
A tool of this sophistication requires commercial support to be widely
accepted.  Especially by commercial developers.

A dumb REXX server is an oxymoron.  The beauty of REXX is that SOMEONE in
the IPC system has to be smart, and REXX is that someone.
That means that programs that use REXX can be brought up extremely 
easily and quickly.  It took only two weeks to provide FULL rexx support 
in Microfiche Filer.  And this includes 27 sophisticated commands, 
a safe asynchronous user abort mechanism, as well as the time to learn REXX!

	cu,
	Gary