MMMMMmmmm – Gen -> Java or Java?
Some questions:
Q1) Should organisations who want to transform their business use Java ?
A1) Yes – why not?
Q2) How should organisations transform their business with Java ?
A2) MMMMmmmm – choices – choices – choices….
The result of this choices issue is that an organisation could choose to migrate their existing applications (maybe mainfame green-screen) directly to hand-crafted Java code, or maybe use a toolset to do this (such as those from Metex and FreeSoft among others).
These tools are no doubt successful and have good track records. BUT what happens 5 years hence, and there is a “new” Java – whatever will be “strategic” then – let’s say “.Net” ?
Another migration, along with all the training and so on that a project of that sort requires ? Yup – that’s reality!
If the organisation had chosen to migrate the application into Gen at the outset, then when the new strategy comes along, the organisation simply deploys into that technology instead.
The costs of migrating to Gen may be higher at the start, but over time, the benefits of technology independance will outweigh them.
This is already well know among the Gen community, but less well publicised outside of it.
