|
Joe Pluta wrote:
Actually, if you want any credibility with me, you will have to establish your credentials. I'm comfortable explaining my background and why that gives me some justification for my opinions. So far, you've yet to do so. You're just sort of telling me "OO is best". Even the OO guys don't do that. And in any event, you're the one who started the personal crap with the "quick hack" comment.
The third party package deal is beaten to death. Yes, you can find some third party libraries. And those are almost all for things which have nothing to do with application business programming. For those things,
But we should define "your" scope of application business programming.
Also, I've seen more than one project get badly burned by incompatibilities between third party libraries. And then what do you do?
No, it seems you don't know what pricing means. You can't follow me, because you've never written an enterprise-level pricing module. I find this all the time: Java theorists use simplistic application "examples" to prove their point, but in truth the real world model doesn't fit.
For example, in pricing you often have to know how much a client has bought in a certain period. This is historical information. You may even have to know which store he bought from, in order to provide quantity discounts. In an OO environment, if you haven't already made that information available to the class that calculates price, you will have to modify the interface. For example, if you only provided the item and customer number to the pricing class, then you will need to add the store number. And as has been shown in every study of OO programming, changes to the interface are the single most expensive thing in OO development. Whereas in a procedural program, it's simply a call to another server.
Excuse me? How exactly do you redeploy an EAR file without restarting the application server? Please show me the EXACT procedures to redeploy an EAR file. I'd love to see this, actually. (By the way, I know you can get around some of this by hot-applying changes, but then you need to know the directory structure of your server, and that gets pretty scary.)
Creating a project with a RPG/JSP mix is the last option i would use when creating a web-based project.
And it's the first one I would use.
Maybe because RPG and COBOL are doing just fine in the business rules space. Most of the concentration has gone on in the Internet programming arena, and frankly we know exactly what happened there, don't we? Basically a highly inflated market of software tat was never delivered, leading to a meltdown of the entire tech economy.
In the meantime, of course, RPG and COBOL keep on going and going...
Marc, you really need to revisit RPG. The changes to RPG have been incredible. As have the ILE concepts and everything else. You're just
Marc, you can spend some time heeding your own words. You called my programming a "quick hack", simply because it doesn't fit into your OO methodology.
This isnt true. See above.
In any event, you have yet to provide any reason that Java is good for business applications. You rant and rave about third party packages and namespaces, but frankly I don't find any real business experience in your statements.
Try this article, perhaps you will find some more.
And I'm not flaming you, I just don't like people coming onto the mailing lists and telling everyone that OO is the way to go when they really don't have the experience to back it up. There might be someone who doesn't know any better who might listen to you. So I am here to make sure the other side of the argument is heard, and to allow the readers to make up their own mind.
Remember, I love Java. I love OO. I think OO may indeed be one of the few true advances in programming since the Von Neumann machine. But I also think RPG is a better language for developing complex business rules, and I have real world examples that, at least to me, prove why. This is based not on a dislike of the language, but on over 25 years of development experience.
regards marc
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.