Java has been on a downhill path ever since Oracle took over Sun Microsystems. The company has been in the news for the security flaws of the programming language. In addition to this, Oracle has introduced a new numbering system for its subsequent patches that has confused both users and experts. Some experts even went as far as saying that this was expected from Oracle considering the horrendous run they have had with Java over the past year or so. If you are taking Java training classes, you can discuss the significance of the new numbering system, and how it might affect the future of Java.
An Insight into the New Numbering System
Oracle released a support document last week, which highlighted how the numbering system would work. The new system will number the limited update releases in 20 and its multiples. Critical patch updates will be numbered using odd numbers. These odd numbers will be calculated in multiples of five, and if the resulting number is even, 1 is added to that number to make it odd.
Reason for this Numbering System
According to Oracle sources, this new system will allow them to release unscheduled updates whenever required. Since there will be a gap in the numbers, the unscheduled updates will have one of the intermediate numbers. Every time Oracle detects a hack or bug in Java, they release an update, but these recent update releases have been given subsidiary numbers, as the numbering system does not have room to accommodate the unscheduled patches.
This new system seems to be another shot in the dark on the part of Oracle, at confusing its users even more than they already are. In a way, it sums up the directionless approach that Oracle is taking on Java at this point of time.
Please Share This Knowledge With Others!