Non-issue. You have to do this anyway, unless you continue to stay in the
monolithic mindset.
In going from monolithic RPG to modular RPG you ARE NOT introducing a new
language but instead expounding on a language the programmer has probably
been using for 10+ years. Big difference in my mind. Not to mention the
fact that they can learn modular RPG in SEU and eventually migrate to WDSC
vs. having a new IDE thrown on them while learning a new language (EGL).
My guess is that it will take an hour.
Once you have it configured properly, there's really little to do on a
day-to-day basis.
When everything goes perfectly of course it only takes an hour. As soon as
it first hiccups it could take a newbie a week to figure something out that
would take you 5 minutes. It takes a long time to get to the point of a
knowledgable J2EE programmer mindset. It doesn't happen overnight as you
are suggesting. I don't believe you are comparing the complexities of
Apache vs. WAS very fair.
Wait, what is your environment?
I would use RPG-CGI, BUT I would also keep RPG programmers from learning
HTML/CSS/Javascript. The key here is to have someone knowledgable about RPG
and HTML/CSS/Javascript discover patterns and build an infrastructure around
those patterns - even to the point of having a compiled "View Engine" that a
newbie RPG programmer can easily use with sub proc calls.
Nathan Andelin has been doing great work in this area and publishing it to
the forums. Obviously not all developers should be writing the one-time
framework code as Nathan is.
Nathan Andelin's codeset is living proof that you CAN in fact develop nice
looking, scalable applications with RPG being used as the ONLY server side
language. This is a huge benefit but you think it is small potatoes, so I
am not going to attempt to convince you. But please recognize that Nathan
has stepped up to your challenges (quite well I might add) that were stated
on this forum in the past.
Aaron Bartell
http://mowyourlawn.com
midrange.com
