EGL puts the i in iPhone
JoePluta 100000KMX3 Visits (2258)
Although it's not really the focus of this entry, I just like saying that. It's such a good marketing phrase; I wish we'd see more like it. And we could, you know - the EGL team is putting together the kind of glitzy eye-catching technology that could be showcased everywhere from a YouTube spot to a Super Bowl ad (do I have to pay to say that?).
I guess though that catchphrase is indeed germane to this entry; in a way it really epitomizes a large part of what I want this blog to be about: moving the i into the future (I'm not going to make all the *i*'s blue this time - bold ought to be enough). I want to really delve into those areas where the particular strengths of EGL and the i work together the best. For example, in the case of the RSDC scheduler, Chris Laffra and I were able to make three technologies - EGL Java/WebSphere, EGL RUI and good old RPG - work together flawlessly. Development was at a pace unlike anything I've done in a long time, and the fact that we could concentrate on the business requirements rather than the plumbing allowed us to deliver code at the speed of thought. It was quite an exhilirating experience, actually.
But what exactly does that mean for my core constituency? What can EGL really do for the long-time IBM midrange customers? These are customers who have entrusted their business to the midrange since it had names like "System/3" and technologies like CCP, customers whose most important asset right now is not even their programs so much as their programmers - programmers with a skill set that all signs indicate is becoming harder and harder to find.
What can EGL do for these folks? Well, in my vision, EGL is nothing short of the wonder drug for these shops. First, it will allow procedural programmers to write web applications. The popularity of languages like Visual Basic and PHP ought to make it clear that not all code need be written in OO, and that procedural programming is still an important otol in the business toolkit. This is particularly good news for business programmers becuase the procedural nature of EGL removes one of the biggest hurdles between RPG/COBOL programmers and the brave new world of the web. The WYSIWYG design tools and the declarative nature of the EGL syntax is putty in the hands of people who have written RPG code.
But if the tool just put a new face on an old paradigm, it wouldn't be the future; it would just be a holding pattern. The future is where EGL really shines. Once you have your business logic encapsaulted in EGL library functions, you will be able to move forward into the world of AJAX and eventually to Rich Web Services (RWS or RUI, depending on which acronym you prefer). But the good news is that you don't have to do that wholesale. You can rewrite parts of your application with JSF (in fact JSF may be all you ever need for large parts of traditional green screen systems) and then apply the new technologies where they are best suited, such as for new executive dashboards or other Web 2.0 types of applications.
I always say thatyou should use the right tool for the job, and for i shops the right tool includes business logic on the i and then EGL for whatever user interface technologies are needed. The beauty is that the right tool for all of the new generation of UI jobs is EGL.