Oracle Courts PeopleSoft's iSeries Users
** This thread discusses the article: Oracle Courts PeopleSoft's iSeries Users **
The emergence of SQL and 4GL is the best thing that ever happened to the IT industry. Why? You compare RPG to SQL as a Pinto to a Mustang. That means you think you can programmer better and faster in your 4GL world. Opinions are great, but how about some facts? Please indicate three quantitative measures showing why SQL is better than native I/O. Use direct measurements, such as the benchmarks I have made freely available at http://forums.plutabrothers.com/IAAI. Next, name three quantitative measures showing how any OO language is more productive than RPG. Finally, define exactly what a 4GL is and what it does. Please show representative code for an MRP generation in the 4GL language of your choice. Identify how long it takes to code such a program, and how long it takes to run on a representative database. I GUARANTEE I can write one more quickly in RPG, and it will run as much as ten times faster as anything you can design. 4GLs are great for queries and reports, and maybe master file updates provided the edits aren't too difficult. But that's not the hard part of programming. The hard part of programming is MRP, or finite forward scheduling, or special pricing, or batch balancing, and I can bet you've never written one of those in SQL or a 4GL that will come close to what I can do in RPG. What 4GLs tend to do is level the playing field. They take away the features that really good programmers use. Come on, Tony, you and me, heads up. Let's have a program-off. I'll write up the specs for an MRP generation. You and I can code it. Let's see who gets done first, and whose actually works. Joe
** This thread discusses the article: Oracle Courts PeopleSoft's iSeries Users **
The emergence of SQL and 4GL is the best thing that ever happened to the IT industry. Why? You compare RPG to SQL as a Pinto to a Mustang. That means you think you can programmer better and faster in your 4GL world. Opinions are great, but how about some facts? Please indicate three quantitative measures showing why SQL is better than native I/O. Use direct measurements, such as the benchmarks I have made freely available at http://forums.plutabrothers.com/IAAI. Next, name three quantitative measures showing how any OO language is more productive than RPG. Finally, define exactly what a 4GL is and what it does. Please show representative code for an MRP generation in the 4GL language of your choice. Identify how long it takes to code such a program, and how long it takes to run on a representative database. I GUARANTEE I can write one more quickly in RPG, and it will run as much as ten times faster as anything you can design. 4GLs are great for queries and reports, and maybe master file updates provided the edits aren't too difficult. But that's not the hard part of programming. The hard part of programming is MRP, or finite forward scheduling, or special pricing, or batch balancing, and I can bet you've never written one of those in SQL or a 4GL that will come close to what I can do in RPG. What 4GLs tend to do is level the playing field. They take away the features that really good programmers use. Come on, Tony, you and me, heads up. Let's have a program-off. I'll write up the specs for an MRP generation. You and I can code it. Let's see who gets done first, and whose actually works. Joe
Comment