Linked by Thom Holwerda on Mon 29th Oct 2007 20:27 UTC
Mac OS X "While the Apple hype machine and its fanatical followers would have you believe that Mac OS X 10.5 'Leopard' is a major upgrade to the company's venerable operating system, nothing could be further from the truth. Instead, Leopard is yet another evolutionary upgrade in a long line of evolutionary OS X upgrades, all of which date back to the original OS X release in 2001. But let me get one huge misunderstanding out of the way immediately: That's not a dig at Leopard at all. Indeed, if anything, Apple is in an enviable position: OS X is so solid, so secure, and so functionally excellent that it must be getting difficult figuring out how to massage another USD 129 out even the most ardent fans. Folks, Leopard is good stuff. But then that's been true of Mac OS X for quite a while now." Additionally, Apple acknowledges installation problems caused by Unsanity's APE, while others are complaining about problems with Java, or visual oddities. Additionally, there are hacks that restore the black dock triangles, opacify the menubar, and to enable Time Machine on Airport disks. Update: It appears the Leopard firewall has a dent in its armour.
Thread beginning with comment 281677
To read all comments associated with this story, please click here.
Lack of Java 6 wasn't my only complaint
by mikeurbandz on Mon 29th Oct 2007 22:08 UTC
mikeurbandz
Member since:
2007-10-29

I am the author of the article cited in the headline about "the lack of Java 6", I would like to clarify a bit. The fact that Java 6 is missing is not my only complaint. It's not even my most serious complaint.

The real problem here, is that not only did they not ship Java 6 with Leopard, but they broke key parts of Java 5 on Leopard, mostly having to do with Java2D. Java2D happens to be a key part of one of my projects. And currently, it is unusable on Leopard.

That, combined with Apple's typical policy of arrogance where they think they have no obligation to their customers whatsoever to keep them informed about why plans were changed, why they yanked previews of software, and when we can expect to see the situation remedied, is really the critical mass point that drove me to give up on Apple. It wasn't just one thing. It was a combination of all three things. And given Apple's long history of keeping their customers in the dark, I don't expect the situation to get any better.

Edited 2007-10-29 22:14

Reply Score: 22

Thom_Holwerda Member since:
2005-06-29

The real problem here, is that not only did they not ship Java 6 with Leopard, but they broke key parts of Java 5 on Leopard, mostly having to do with Java2D. Java2D happens to be a key part of one of my projects. And currently, it is unusable on Leopard.


Thanks for the clarification, Mike. I updated the article to make the complaint a bit more general.

Sorry for the inconvenience.

Reply Parent Score: 2

segedunum Member since:
2005-07-06

The real problem here, is that not only did they not ship Java 6 with Leopard, but they broke key parts of Java 5 on Leopard, mostly having to do with Java2D. Java2D happens to be a key part of one of my projects. And currently, it is unusable on Leopard.

Yer. Apple doesn't get backwards compatibility either, even in places where you would think it would be easy to keep.

Reply Parent Score: 2

mikeurbandz Member since:
2007-10-29

Just as an update on the Java2D situation, it turns out there is a workaround for this that a few people have pointed out to me. For those of you who are experiencing slow performance problems with Java in Leopard, you can issue the following parameter to to Java when you start it:

-Dapple.awt.graphics.UseQuartz=true

On Java 5 in Tiger, the default rendering pipeline was Quartz. For some reason, however, Apple decided to switch the default rendering pipeline to the standard Java one on Leopard. The standard Java one is not accelerated, and thus the slow performance.

Why Apple decided to change the default pipeline is beyond me. On most other platforms, Java uses the OpenGL pipeline by default. And until now, it used the Quartz pipeline on Apple. But none of the other platforms were still using the plain old unaccelerated Java pipeline anymore.

You can read more about the Quartz pipeline switch here: http://weblogs.java.net/blog/fabriziogiudici/archive/2007/10/leopar...

Reply Parent Score: 2