Re: EGL vs. Java

Joe Pluta skrev den 31-01-2008 19:12:

But the good news is that, written properly, web applications on the
System i are as fast as green screens. I've got browser-based applications flipping pages quicker than the eye can see without making the server break a sweat. So the trick is, how fast can you create these applications. The problem up until now was the learning curve of Java vs. the lack of tools support for CGI. Both of those are gone with EGL.

This sounds good. I have spent a LOT of effort trying to get Java stuff to run well (still doing so, fun to learn) on the i, and the major reason we do it in Java is basically that I _know_ Java and can use that knowledge again elsewhere. To start learning, using and marrying EGL one of the things that is crucial is "will this technology also be here in 10 years, because our application will"?

We have looked at HATS, others have looked at VARPG, and I am not the decision maker but even I as a newcomer has a general feeling that you cannot DEPEND on these things being there for you in X years. That makes me and my very conservative colleagues very reluctant to even LOOK at these smart new things. We do not have time to invest heavily in blind alleys.

What are other peoples experiences with this?