Re: Why keep "old" code (Was RPG III)

I'm sure I'll get some heat for this, but there are some instances
where "if it ain't broke don't fix it" does have some (small) merit.

Why beat yourself up over not having the resources required to
modernize an entire package on your own?  Why not let vendors do their
job?


Most companies that purchase a source code license from a vendor won't
have the resources to maintain and update the package on their own
indefinitely, and at some point the vendor needs to take on that task
and spread the cost over multiple customers.



Suppose there were 1,000 JDA customers with source code licenses, and
they all were trying to modernize their versions of the package
independently of one another.  What a huge expense that would be!  The
job of the vendor is to pool customer resources and gain an efficiency
from economies of scale.



Nathan M. Andelin





 
____________________________________________________________________________________
8:00? 8:25? 8:40? Find a flick in no time 
with the Yahoo! Search movie showtime shortcut.
http://tools.search.yahoo.com/shortcuts/#news