Reply to thread

Message: [QUOTE="Lew, post: 3698776"] At my day job half the Java infrastructure is just coming in to Java 1.4, the other half to 1.5. The problem is widespread. I would guess that the usage is higher for 1.4 than your guess, and Java 6 is much lower. But I'm in the position of trying to guess the shape of an elephant knowing only the feel of its ears. If I had the ears of the decision makers where I work, I'd suggest to them that the risk of continuing with Java 1.4, with its insufficient concurrent memory model and slower performance than modern versions, exceeds that of the conversion to Java 5, especially in our environment which involves multiple nodes with multiple processors running multiple JVMs with various forms of communication between them processing high peak volumes of information per unit of time under tight time constraints and rigorous availability requirements. Some similarly high-demand production Java code I've seen runs about three times faster under Java 5 and the associated Java EE (J2EE) servers than it did with older platforms. Not just CPU-bound code, but all sorts of different stuff involving messages and files and databases and the like. Obviously Java by itself is only a piece of that improvement - the app-server vendors were busy improving their stuff, too. The fear of upgrade that I've witnessed was based on considerations of product reliability on a new platform, cost of code conversions (rooting out misuse of the 'enum' keyword and the like), and operations costs associated with migration to and maintenance of the new enterprise platform. Decision makers seemed utterly unimpressed with claims of performance improvement; only risk mattered. Lately I have been meditating on the balance of risks between those that arise from conversion and those that arise from the failure to convert to Java 5 or later. I posit that risk comparison will carry more meaning to decision makers than benefit comparison. [/QUOTE]

Verification