JCArticles

Java has come along a long way. Many would agree with this. I did not until the Java 1.5 "Tiger" hit me. The tiger had several new features, and more importantly, it has new syntax. Six major upgrades that the tiger presents are certainly the generics, enhanced for loop, autoboxing (unboxing), improvement on Typesafe enum, Static import and the metadata. Of course there are many more, which can be found at java's official site. Out of these six, at least four would be used in my daily "programming" life. From java 1.1 to 1.4, it seemed more like new frills were simply added. It felt like earning more brownie points when you downloaded the newer version. But should I start using 1.5 immediately, maybe not.

The developers and programmers (if you distinguish between them) are left with one great dilemma (me too). It certainly is as to which version to use when preparing software in java. This problem hides itself under the carpet when you are programming for a specific client with a specific system where you can get it upgrade on site, but when the app is going to be used by Mr. Williams from South Africa and Ms. Lee from Japan, you really have to give a thought as to whether your app is going to run on both the systems (that is why java was made in the first place, isn't it?). I've always had the latest version of the sdk, yet I would try and target compiling in a lower possible version, so that even those people would be able to use the apps, who were, well, frozen in time and didn't go up the "version ladder". For e.g., ordinary applets, by me and my company, in most of the cases would be compiled in java 1.1, so that no user ends up waiting for an hour before the plugin for the latest version is downloaded and installed (get yourself a coffee if your yawning). For e.g., once on a tour, I happened to visit some site in a cyber caf