I'm not having any problems with Mail, Safari or any other Apple made software for that matter... and im using an old Powerbook G4 1.6GHz. The only thing I've noticed is the jerky animations with the dock and exposé/Spaces. How do you ppl keep breaking your Leopard?
You do know that Java is supposed to be platform independent right? Besides this is only a Developer Preview, Im sure the 32bit UB will be out soon
The point I was addressing is the viability of pre-existing non-64 bit Apple hardware.
Obviously any future systems I buy will be 64 bit only.
For now, I've already got 64 bit Linux hardware. I'm currently on 32 bit hardware awaiting the next Mac Pro lineup.
I don't see any advantage of Java on OS X from the Server perspective.
I don't plan on dealing with any Client app work for Java in OS X--this is where Cocoa should be the focus and where I'll put my efforts on the matter.
Apple should make an actual strategy on what they will focus on with regards to Java against other language tools and technologies.
To make a simple and clear declaration that Apple will focus solely on Java for the AppServer or just another option would clear up a lot of confusion.
Apple should not focus on Java for the client. Let Sun focus on that since it's their platform for client/server development.
I was quite disappointed for several years where we saw an attempt to appease all camps from Java to Carbon to Cocoa.
Cocoa should have always been first from day one.
Carbon should have been the transition strategy as it was stated back in 1997 and not this abysmal 10 year delay to Cocoa full-steam ahead.
How the hell Java ever became on equal footing with ObjC was an attempt to make Apple the first to "embrace" Java integrated into their OS. Big deal. That should have been Sun's duty with Solaris.
If I were chief of the Enterprise Group that was once NeXT and then for a while AES at Apple it would be clear:
WebObjects 6 (Pure Cocoa/ObjC 2.0/Python/Ruby/AppleScript)
Java 6 (Legacy for WebObjects 5.4.x, but included in OS X Client/Server at a platform agnostic point of view. Make it current with the OpenJDK and move forward with it in-line with the rest of the Industry)
If Apple isn't going to make WOF a major player in the Java World they should reign it back in to the Cocoa world and use it to extend in-roads into other markets where a Distributed Objects/Client-Server/WOF 6 ObjC 2.0/Heterogeneous mixed set database backend clients can be better served.
Make WebKit a crucial part of the strategy for the Enterprise and extend it to add value to their consulting services teams.
If you're not going to be a Hardware/Software solution provider for more than the creative fields and general consumer don't waste your stock investors time and money on put resources partially into it.