Apple And Java 1.5
By Adrian Sutton
Sun released Java 1.5 (or 5.0 or something) yesterday and today suddenly there’s a whole bunch of people complaining that Apple hasn’t yet ported it to Mac OS X. What the? People do realize that porting the JVM takes time right? Apple don’t get the final source code from Sun until Sun finish it (oddly enough) and Sun only just finished it. Sure Apple has had access to prerelease builds from Sun (and similarly Apple Select and Premiere developers have access to a seed release of Java 1.5). It will take time to for Apple to port the JVM and add in all the extra little details they provide (where little amounts to an entire L&F plus more). Then it has to go through QA (you do want it tested right?) and then it will be released. Daniel Brookshier” leads the charge with the whining. Of particular note is the comment:
Versions of Java 5.0 are released for Linux, Solaris, and MS. When will Apple release 5.0? Not really sure, but the rumors are that the sometime next year when Apple releases their next release of OS X. That’s a long wait for someone that needs to be building products with the latest and greatest. Firstly, versions of Java 5.0 have been released by precisely one vendor (Sun) for the platforms that they support. When will Apple release 5.0? When they’ve had a chance to work on it. Secondly, “needs” to be building products with the latest and greatest?? Exactly what feature is present in Java 5.0 that you absolutely have to have? Sure there’s a lot of nice stuff and I can understand the desire to want to use it, but need to use it? I think not. Besides which, right now there are effectively zero users out there with Java 5.0 installed – it hasn’t even come through the automatic update system for me yet. Most developers still aren’t crazy enough to install Java 5.0 on their main dev boxes and anyone speaking Arabic or other RTL languages definitely won’t be upgrading (big thanks to Igor for the work around on that one). Take a deep breath people, calm down and use some common sense. Now is the time when you should start considering dropping Java 1.3 support if you haven’t already and doing testing on Java 1.5 to make sure your product runs on it correctly. In 6-12 months when the new release has stabilized and been deployed widely you might start thinking about dropping support for Java 1.4 and taking advantage of Java 1.5. There’s no rush, it’s not going to suddenly disappear and leave you stuck behind. However nice the features might be, you’ve survived without them this long right?