|
Not getting at you specifically Bob but ...
If it isn't broken, don't fix it,
Sorry - I don't agree and frankly think that this philosophy is doing more to kill the platform than anything IBM has or hasn't done in terms of marketing. VB3 program probably weren't broken when moved to VB4, 5, 6 ... But how many VB3 programs are out there today? VB4 came out _after_ RPG IV! The problem is two fold. First of all programs are just about always broken - they need maintenance. I believe that by keeping them in RPG400 the maintenance takes longer than it need and the programmer is forced to use "old fashioned" methods to solve their programming problems. Secondly when the user asks for enhancements the decision has to be made as to whether to do it in the old way or convert and do it the new way. Often the decision is that "it's not broken" so they do it the old way. Another opportunity missed. Another possibility that the new CIO will look at the Apps and describe them as old-fashioned green-screen rubbish. Another nail in the coffin. If my programs are in RPG IV them adding new features, plugging in things like Excel spreadsheet creation, adapting them for web, etc. etc. become easier. We're going to ride "it ain't broken" into the System's grave! (Ducking and running!) Jon Paris Partner400 www.Partner400.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.