RE: Legacy code

Tim, 

>>But the decision isn't just "what's the best". It is "what gives MY
>>clients the best ROI." Sometimes those are different answers. Some
>>shops have reason to be coding Java TODAY. Some have reason to be
>>coding RPG II..
><<..snip..>>
>
>But surely, when looking at return on investment, one should also be
>considering competitive advantage. You're not going to try and tell me
>that someone is going to maintain any semblance of competitive
>advantage by coding new RPG II. Even maintaining it has got to have a
>cut off point - frankly I ache looking at tricky cycle stuff, and I
>think the same is true for most newer /400 developers..

New code is always better looking than old code, if only because one is
more experienced now.  It isn't necessarily the language that is 
providing the "goodness" or "badness" of the code; a lot depends on
the experience level of the programmer...

Buck Calabro
Commsoft, Rensselaer, NY

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---