Re: EGL FUD - was: JSF/EGL datatable positioning question

Bob,

Is it important not to confuse EGL with JSF because EGL is a Java and/or
COBOL generator, and not an actual programming language?

And if COBOL or Java are my choices of what EGL generates, why would I spend
any money replacing all my RPG applications with this kind of tool? Why
would I not continue to use RPG? There are many tools to get me to the web
with RPG that require much less investment than a new language-generator, so
I am confused as to why certain IBM employees, such as yourself, continue to
push the EGL religion, while most i5/OS IBMers tell us RPG has a strong
future.

We keep hearing of your suggestion that EGL should replace RPG. This
concerns most members of the community, excepting a few who have drunk the
koolaid. If customers feel that their only modernization path is to replace
everything with a language that simply generates other languages (COBOL
being one), we are all going out to buy LANSA or BCD tomorrow, since those
are cheaper and more productive paths to our future.

Modernization has rarely been a "throw everything out and replace with xxx",
yet it seems like the EGL proponents at Rational would like us to do this.
Can you stop this FUD, or explain why you wish the midrange community to
spend huge dollars on replacing everything with this generator tool with no
apparent business ROI? I understand this would help IBM revenue, but it does
not make financial sense in any way to System i customers.

Trevor




On 12/16/07 10:29 AM, "Bob Cancilla" <bob.cancilla@xxxxxxxxx> wrote:

Folks,

You may want to post this and other technical questions about EGL to:
http://www.ibm.com/developerworks/forums/forum.jspa?forumID=435. This is
the IBM DeveloperWorks forum for EGL. It is monitored by the development
staff and other expert EGL users who usually respond within 24 to 48 hours.
This forum is dedicated to answering "how to" questions.

BTW, Joe is correct in his statements, understanding how Java and JSF
handles the solution is not necessarily the best way to handle issues in
EGL. The whole point of EGL is to hide the underlying technology so you
don't have to deal with it. This will become even more of an issue as we
roll out our next version of EGL with WEB 2.0 support where we provide
advanced UI capabilities that leverage Silverlight, DoJo, in addition to
AJAX and advanced JavaScript. All of the supporting JavaScript, JSF, XAML,
and other technology code is hidden and generated by EGL. We have been
doing webcasts and demos of this new facility which will be announced and
shipped in 2008.


I've asked our experts to look at this specific question and will respond
here when I get an answer. The most direct path to EGL Q&A is the
DeveloperWorks forum.