• Subject: RE: Why MI? (Was: MI programmers list? Interested?)
  • From: "Dan Bale" <dbale@xxxxxxxxxxx>
  • Date: Wed, 10 Nov 1999 14:08:43 -0500


I think the quest for MI and C lies in being able to do something useful that
could not be done in RPG (or done reasonably).  I would most likely only use it
in utility code, you know, stuff that could break and not disrupt company
operations.  For production code, I would favor APIs when available over MI or
C.  Any MI or C code in a production environment would have to be tested,
tested, tested.  And documented to the hilt.

It (almost) goes without saying that MI would never be used to write, for
example, a whole A/R application.

- Dan Bale

boothm@earth.goddard.edu wrote:

Isn't this quest for MI and C really beyond the scope of most RPG shops?
Isn't the goal of RPG the idea of having a sustainable and understandable
body of coherant code?  Once one wanders into the esoteric solutions
hasn't one destroyed a shop's code base?  I believe there's a place for
that coding but it isn't the vast majority of business application shops
is it?

To be truthful it bothers me to see people reaching out for complex
solutions to trivial problems, and as a result leave a shop with code that
is difficult to maintain and never really understood by anyone.  It is a
little bit like tweaking case tool code; once done, the nightmare haunts

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].