«« Properties Get More Difficult Google Group for AudioMan and Durham »»
blog header image
Durham Not Using Java 5

I'm going to have to backpedal on using Java 5 for Durham, one of the main reasons being that the Mac doesn't support Java 5 yet. Apple releases their own versions of Java instead of Sun and they usually trail the Sun releases by a few months. Java 5 (Tiger) is apparently going to be released with Mac OS X 10.4 (also called Tiger).

Since I'm trying to position Durham as metadata support for Eclipse RCP applications it doesn't make sense to not support the Mac, one of the three major platforms Eclipse/RCP is written to. Another reason is that people are still using Java 1.4 to make software and they may not be able to use Durham plugins because they haven't upgraded to Java 5 yet.

I can't wait to use Java 5 features but unfortunately Durham is not the right project to use them just yet.

Posted at January 13, 2005 at 01:20 PM EST
Last updated January 13, 2005 at 01:20 PM EST
Comments

Wow. I had no idea that Sun didn't produce Java for the Mac. I find this kind of interesting considering that they support Linux and Sun Solaris Unix. Mac OS 10 is just a variation of Unix. It probably wouldn't be that hard to make a Mac version. Oh well. I'm sure it has a lot to do with the fact that they are really pushing server Java and don't really care that much about desktop Java. Which is about the only thing Mac's are used for nowadays.

» Posted by: Kibbee at January 14, 2005 08:37 AM

I think it has more to do with the fact that Apple wants to control it.

» Posted by: Ryan at January 14, 2005 09:10 AM

I guess Mac would have had to strike some kind of deal with Sun to do that. It's probably in Sun's best interest to have Java up-to-date for Mac. Anyway, has anybody seen the new MiniMac. I think I want to buy one.

» Posted by: Kibbee at January 14, 2005 09:30 AM

Sun allows any company to make their own Java VM, as long as they follow the restrictions set out by Sun. There are thousands of unit tests the VM has to pass before it will be approved as Java by Sun.

IBM makes their own Java VM. Microsoft did at one point but changed Java so much that Sun ended up taking them to court over it and the revoking their certification. Then Microsoft made C# and the .NET framework.

» Posted by: Ryan at January 14, 2005 09:35 AM

I understand letting Mac make their own Java VM, but why not have a VM for the Mac Environment. Imagine if Macintosh broke the rules, and then Sun took their license away, or if they just decided they didn't want to do it anymore. There would then be no more Java VM for Mac. Sounds like Sun should have a VM for Mac Users, and stop depending on Macintosh to provide one.

» Posted by: Kibbee at January 14, 2005 12:25 PM

It's in Apple's best interest to have a Java VM ... it won't be going away. :)

» Posted by: Ryan at January 14, 2005 12:27 PM

It was in Microsoft's best interest to have their own VM. That's why they had one originally. Then they went and lost their license. Now they have no more VM. Windows users now have to have the Sun VM. What if this were to happen for apple?

» Posted by: Kibbee at January 14, 2005 05:03 PM

Windows users can use the IBM Java VM if they don't want to use Sun's. That's IBM hedging their bets.

It was in Microsoft's best interests to do exactly what they did: hijack Java and make it do Windows-specific things. Sun didn't like that and now Microsoft doesn't make a VM, which is good.

It's good because not only does it prevent Microsoft from breaking the (almost) "write once run anywhere" property, but it also gives Java some competition with .NET. That competition brought us some of the new stuff in Java 5.

It's in Apple's best interest to make their own VM because they'll want to control how Java works on their own operating system. Apple has more at stake to make sure Java performs well and looks good (Swing/AWT). That's probably why they do their own port instead of leaving it to Sun.

I remember reading that Apple was going to position Java more prominently in Mac OS X but instead stuck with Objective C. Java is still well integrated into Mac OS X though and performs pretty well.

» Posted by: Ryan at January 14, 2005 05:12 PM
Google
 
Search scope: Web ryanlowe.ca