|
> From: CWilt@xxxxxxxxxxxx > > But, I don't think you can draw the line saying procedural for business > logic and OO for presentation (or whatever) so firmly. Actually, Charles, yes I can. I am in fact doing just that: I am stating, for the umpteenth time, that procedural code is better for business logic than OO. Just like I can say that native I/O is better than SQL for transaction processing, and just like I can say that EJB is useless for just about anything. I can say these things: A) Because they're my opinion. B) I've got enough experience in the field writing every kind of computer program in every kind of computer language that my opinion bears at least a little weight. > Which is fine, we can agree to disagree Joe. I keep an open mind about > it. Maybe you'll convince me. Actually, I don't really want to convince you. I'll present my viewpoint and, if you rebut, I will point to what I consider the error of your ways. If you don't think my opinions hold water, then by all means do your own thing. But if you post publicly that OO is a good idiom for business rules, I will respond. Joe
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.