RE: 520 pricing structure

> From: albartell
> 
> Half of those are needs based on existing knowledge sets so I wouldn't
> count
> them as valid arguments (i.e. PASE, RPG, COBOL). Personally if I was
> writing
> a new application (with a GUI front end) I wouldn't write it in RPG or
> COBOL.

This is one place where we differ.  RPG is the best language available
for writing business logic, Aaron.  It's better than VB certainly, and
FAR better than Java.  See, I believe in the right tool for the right
job, and using an RPG back end to a JSP front end delivers all of the
flexibility and power of a real business language along with a
sub-second response time.

(Literally.  I just installed a system using my thin-veneer JSP approach
and we're getting sub-second response time on 300-record queries.  We
downloaded over 8000 records to the browser in around 10 seconds.)

I think part of our disconnect is due to the fact that we don't agree on
what an "application" is.  If all you're doing is queries then it
doesn't matter what language you use, and you can run the thing on a
Kaypro for all I care.  But if you want real business logic -- material
scheduling, pricing, forecasting, warehousing, logistics -- you need a
real business programming language, and RPG is the best.

Joe

P.S. As to the Struts/JSF fiasco, you are definitely trying to make
roadkill smell like roses.  The problem is that one is not compatible
with another.  It's NOTHING like RPG III to ILE RPG.  And when
McClanahan dumps JSF next year (or whenever he gets tired of it), you're
going to have yet another set of obsolete technology.