Tweet
Top 10 Things RPG Needs
** This thread discusses the article: Top 10 Things RPG Needs **
Builder said "we should want, no demand, a new universal language from IBM. Why are we limiting ourselves?" I hate to use the term "legacy", because it sounds so pejorative. Sort of like a conservative using the term "liberal" in such a fashion that "liberal" actually means something less than despicable. But until a better term comes along, I suppose "legacy" will do. There are tens of thousands of firms who rely on RPG, and even COBOL, to handle their daily business needs. These firms have a great deal invested into every single solitary line of code, and there are hundreds of thousands of lines of code for every firm. The business work, the code works. To ask any business entity to scrap the legacy investment, simply because one does not like the delivery method is bad business. Most firms will move if they are convinced that there is a solid business reason for doing so. Even then, a wholesale move is not usually an option. In a poor business climate, those who have stuck with legacy techniques have fared better in TCO, and ROI than those who have jumped on other bandwagons. When you consider cost per line of code over the entire enterprise (this includes maintenance and time of development) RPG comes out very well indeed. The interesting thing is that (graphics aside) there is very little difference in quality, and quantity of the final information delivered from platform to platform. Most execs, and managers are only interested in what they get into there hands, and not how it gets there. Dave
** This thread discusses the article: Top 10 Things RPG Needs **
Builder said "we should want, no demand, a new universal language from IBM. Why are we limiting ourselves?" I hate to use the term "legacy", because it sounds so pejorative. Sort of like a conservative using the term "liberal" in such a fashion that "liberal" actually means something less than despicable. But until a better term comes along, I suppose "legacy" will do. There are tens of thousands of firms who rely on RPG, and even COBOL, to handle their daily business needs. These firms have a great deal invested into every single solitary line of code, and there are hundreds of thousands of lines of code for every firm. The business work, the code works. To ask any business entity to scrap the legacy investment, simply because one does not like the delivery method is bad business. Most firms will move if they are convinced that there is a solid business reason for doing so. Even then, a wholesale move is not usually an option. In a poor business climate, those who have stuck with legacy techniques have fared better in TCO, and ROI than those who have jumped on other bandwagons. When you consider cost per line of code over the entire enterprise (this includes maintenance and time of development) RPG comes out very well indeed. The interesting thing is that (graphics aside) there is very little difference in quality, and quantity of the final information delivered from platform to platform. Most execs, and managers are only interested in what they get into there hands, and not how it gets there. Dave
Comment