Weiqi Gao's Observations - mac tag

Apple Releases Java 6 for 32-bit Intel and the iPhone

Wed, 01 Apr 2009 12:11:12 GMT

Apple: We are pleased to announce the immediate availability of Java Update 7 (including JDK 1.4.2_30, JDK 1.5.0_22, and JDK 1.6.0_13) for OS X 10.3.5, OS X 10.4.3 and OS X 10.5.1 on 64-bit Intel and G5 platforms as well as 32-bit Intel platforms.

JDK 1.6.0_13 is additionally available for the iPhone and the iPod Touch devices.

Finally, I can get some up to date Java for my ancient Mac!

SoyLatte To Be Integrated Into OpenJDK

Fri, 18 Jul 2008 03:56:35 GMT

(Via robilad.)

Landon Fuller:
Sun Approved: Merge from BSD Java to OpenJDK

Sun has approved merging the JRL-licensed BSD Java to the GPLv2+ClassPath OpenJDK-6. That means that all of the BSD Java changes, including the SoyLatte Mac OS X port, can now be sent to the OpenJDK project, and an official BSD porters group can be proposed: ...

Dalibor mentioned this in his comment on this blog yesterday.

He also mentioned Cygwin and Mingw32 as possible purveyors of OpenJDK on Windows platforms.

An interesting idea...

<grin i-can-hear-adam-say="But Cygwin is not a platform!"/>

SWT Detractors, Rejoice...

Wed, 30 Apr 2008 12:45:55 GMT

... for it doesn't work with the newly updated Java SE 6 On The Mac:

Chris Adamson: I think you have that backwards. Apple's JVM has been Cocoa-based for a while now (since 1.4). SWT is Carbon-based. And even that wasn't a deal-breaker before. The real problem seems to be that:

The new JVM is 64-bit Intel-only

You can't mix 64-bit and 32-bit code in an OSX process

Carbon is 32-bit only and apparently will remain that way

SWT is Carbon-based

For what it's worth, QuickTime for Java won't work on the Mac's Java 6 for exactly the same reason. Carbon is de facto (but not de jure) deprecated, and therefore any Java libraries that use Carbon are in big trouble.

Jess Holle:
Nigel wrote:
> wow, the thread http://www.eclipsezone.com/eclipse/forums/t97750.html
> has been locked down because they didn't like people telling them that
> SWT was a bad idea....

For most use cases and development, SWT seems to be one of those ideas whose time has come and gone...

I'm sure porting SWT from 32-bit Carbon to 64-bit Cocoa is something that is doable but will require some time and effort. The question is: "Is it being done?"

It seems it's time for Eclipse users to be patient, as Swing users were patient in the last ten years.