Gregory has posted 1 posts at DZone. View Full User Profile

Apple finally releases Java6 for Mac OSX

  • submit to reddit

According to the Apple website Java6 has finally been released for Mac OSX 10.5. No further details were given about support for other operating systems.

"About Java for Mac OS X 10.5 Release 1
This Java for Mac OS X 10.5 Update 1 adds Java SE 6 version 1.6.0_05 to your Mac. This update does not replace the existing installation of J2SE 5.0 or change the default version of Java.

This update provides Java SE 6 version 1.6.0_05.

This release does not change the default version of Java. This release is only for Mac OS X v10.5.2 and later, and should not be installed on earlier versions of Mac OS X. This release is for 64-bit Intel-based Macs only and cannot run on PowerPC-based or 32-bit Intel-based Macs.

Software developers can visit the Java Reference Library for information on this release's features."

Published at DZone with permission of its author, Gregory Pierce.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


Mark Haniford replied on Wed, 2008/04/30 - 11:55am in response to: Mike P(Okidoky)

As a Java developer, I wouldn't touch them with a ten foot pole. Linux is better.

Maybe for "you" it's better, but not for me. But let's not turn this into a stupid OS wars thread.

Onno Scheffers replied on Wed, 2008/04/30 - 4:52pm in response to: Bodo Tasche

Are you sure about that? I just installed it and Cyberduck still works fine here

Jonathan Locke replied on Wed, 2008/04/30 - 6:49pm

Sadly it's a couple years late and doesn't run on my laptop.

Mike P(Okidoky) replied on Wed, 2008/04/30 - 9:29pm in response to: Mark Haniford

I meant to say that Linux does Java better.

Bodo Tasche replied on Thu, 2008/05/01 - 12:37am in response to: Onno Scheffers

[quote=ohno]Are you sure about that? I just installed it and Cyberduck still works fine here[/quote] Open Java-Preferences, set java 6 as default vm and try to start cyberduck.

Onno Scheffers replied on Thu, 2008/05/01 - 4:47am in response to: Bodo Tasche

Ah ok... I thought you meant that simply installing it will break apps, which it doesn't. You need to manually set it to be the default VM before apps break, which makes sense.

I guess that's why the installer doesn't change the default for you :o)

 Java 5 as default is fine with me but I'm happy I can now finally pick Java 6 if required. I'm sure the apps will be fixed quickly enough to cope with the update.

Bodo Tasche replied on Thu, 2008/05/01 - 5:08am in response to: Onno Scheffers

[quote=ohno]Java 5 as default is fine with me but I'm happy I can now finally pick Java 6 if required. I'm sure the apps will be fixed quickly enough to cope with the update.[/quote]

 Sorry, but this can't be fixed by the apps. The apps use the cocoa-bridge Apple
 provided for the vm. But Apple decided not to deliver a cocoa-bridge for 64bit Java. This means that no Java app can use cocoa to make the app more comfortable to use under Mac OS.

 Apple made a big error in releasing this VM in that broken way. And they now it.

Onno Scheffers replied on Thu, 2008/05/01 - 5:20am in response to: Bodo Tasche

Apps can always be fixed, even if it means dropping the use of an existing library. It just makes things harder.

I'm not worried. Every time Apple releases (or doesn't release) an updated VM, people seem to be angry or unhappy. After the critisism dies, Apple usually quietly fixes the issues if the software-authors haven't worked around them yet.

Sure it's not ideal and means we have to wait longer. But if you want to work with the latest version of Java, you know you shouldn't be using a Mac. Apple focusses on other things long before they look at bringing Java up-to-date properly.

Mike P(Okidoky) replied on Thu, 2008/05/01 - 9:49am

Isn't it possible to write a Java app with a Mac look and feel that's not sensitive to those little Apple add-ons?

Java is supposed to be write once run everywhere, and it is.  Something that stops running after an upgrade is an exception in my books.  I have experienced minor problems mind you, but 1.5 to 1.6 was pretty smooth for the products I was working on.

I took a peek at this Cyberduck application, and it doesn't look like it should be too hard to write this as a normal portable Java application I'd think.  Why do Mac people want to be different?  What does this Cocoa thing do that Java can't natively for an application like Cyberduck? 

Bodo Tasche replied on Thu, 2008/05/01 - 10:04am

E.g. Growl is a nice feature you could use. It's an application notifier system nearly every mac user has installed. The only way to use at the moment this is the Cocoa-Binding.

TV-Browser (the application I am working on) is running under mac, linux and windows. On each platform it has a little bit code that makes the application a nice desktop application for each platform. 

If you want a good app that feels "right", you simply have to do this.

Server-Applications don't need to be platform specific, a migration to 1.6 is smoth for those products.

Onno Scheffers replied on Thu, 2008/05/01 - 6:36pm in response to: Fabrizio Giudici

[quote]This sounds way too simplistic! For an application based on Cocoa, dropping Cocoa means to rewrite the application.[/quote] 

Yeah, but if it is indeed just a Java application that depends on some libraries to bring in some native functionality/ui (haven't checked.. just going by the information in this thread), then it can be largely worked around. Anything Cyberduck can do, can be done with plain Java as well. If the application needs to be written from scratch in order to remove those libs, then something is really wrong with the project, which I doubt.


[quote]And as Bodo says, there's no support for Java 6 for PPC and Intel 32bit, which is *deeply* annoying. I'd like to be wrong, but I bet this won't be ever fixed.[/quote]

Just pointing out that every time Apple does something people tend to overreact (both negative and positive). Java on Mac is not Apple's first priority and if you want the latest and greatest in Java, you shouldn't count on Apple to bring it to you.When Leopard was released without Java 6 we heard stories of doom about Apple completely dropping Java support and never releasing Java 6 anymore. Now they released Java 6 and there's stories of doom about how they broke everything and how this will bring an end to Java-development with OSX.

I think we all agree that support could be better, but that simply won't happen until Sun or the community comes up with a port of the real thing. Until then, I'm glad that Apple still seems to support Java and I'm sure improvements will come with the next couple of updates.

So basically nothing changed: targetting Java 6 in your applications or applets is still a bad idea, since most Mac users don't have it and even if they have it, it won't be the default VM. But at least it is possible now to use Java 6 and Apple has shown they are still working on it. No reason to overreact IMHO.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.