Re: RPG and AJAX was->RE: How do I create a webpagethat....

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Bob Cozzi
> 
> Joe, what's your point? This is like saying the grass is green and the sky
> is
> blue. You can say this about everything, from JAVA/JSPs to RPGIV to CL to
> C/C++
> to Python to Perle to PHP.
> What's the point?

My point is that AJAX is a technology looking for a reason.  There just
aren't many places where it's really necessary.  Yet it will be overused
because right now it's bright and shiny.


> Ajax is here to stay it is the next cool toy/tool to play with.

Basically, this makes my point.  There is a certain class of programmer who
will push AJAX because it's cool, regardless of the utility of the
technology in the business case.  It's the new hammer syndrome.


> It will displace
> a lot of Java/JSPs that's for certain, but it will also enable people who
> shied
> away from the JSP or similar model to get into web development using just
> JavaScript and RPG IV (or pick the host language you prefer most).

I disagree.  Nothing in AJAX displaces JSP, since you can use AJAX in JSP.
In fact, AJAX is an interesting way to make use of integrating JSP and CGI.
Unfortunately what AJAX does is move server logic to the client by pushing
it into JavaScript.  Of all our currently available tools, JavaScript is by
far the hardest to debug.  Using it to turn a web browser into a thick
client is a bad idea except in those instances where you specifically need
thick client functionality.


> I see 80 percent of RPG IV code out there is poorly written due to rushing
> through it or perhaps indifference on the part of the programmer. I see
> this in
> most applications in other languages as well. "Make it work for my
> specific situation and nothing more."

This is a non sequitur.  Tailoring a design to a specific business
requirement does not lead to bad code. 


> I just helped out a hospital software company and the Ajax implementation
> of their hospital registration and lab coding software is killer now
> compared to the old green screens. And it runs faster!

And my guess is you could have done the vast majority of the code without
AJAX.


> Lest we forget--5250 use interactive CPW where as Ajax uses CGI which is
> batch CPW.

Bob, you're all over the map.  JSP is batch as well.  In fact, any HTML
generation short of the old WebFacing is batch.


Again, just in case I'm not being clear: AJAX is not a bad technology.  It
has uses.  However, it should be a business decision as to whether to use
AJAX, not a decision based on "coolness".

Joe