Reasons why MAID applications can only be faster than REXX 
applications.

1. MAID objects are loaded once into memory and pre-compiled.
   All new instances used the pre-compiled code in memory.
   A standard REXX command file have to compile every time.

2. Routines that require a great deal of calculation can be put in a
    C dynamic link library and this can be called from a MAID module.

3. MAID sub-commands and functions do work fast - that would
   otherwise need to be done in REXX in addition to providing a
   Presentation Manager interface (not available in REXX).
   Controls are treated as REXX variables which means there
   is no need for REXX I/O statements in the MAID generated 
   scripts - i.e. shorter  scripts.

4. MAID objects and controls can interface externally to each other
   and from external C code by dialog and control name.
   As a result, truly modular dialogs can be developed that are 
   independent  of the code that needs to use them.
   Dialogs can be quickly and easily customised without affecting 
   code that use them.
   Dialogs can be re-used by many applications easily without re-design.
   This results in speedier development and smaller modules.
   Smaller modules mean they are easier to maintain and update.
   Standard C code can send and wait for events from controls -
   this means a PM interface can be given to existing C routines
   without major re-structuring to a windows format.