Apple on Friday seeded a new build of Mac OS X 10.3.2 to developers, as well as a new version of Xcode 1.1. Also, Apple on Friday seeded the second developer preview of Java 3D and Java Advanced Imaging, two APIs that extend the Java platform.
Heh. A pity in what way? Because Sun isn’t eating their own dogfood, or because Apple shouldn’t be pushing Java, as Java isn’t good enough? (the second isn’t my opinion per se, but just one way the statement could be interepreted) It is a pity to me in a couple ways, but generally a good thing. Sun pours millions and millions of dollars into Java marketing, even if they don’t use it themselves much. They certainly are pushing it more than Apple in most ways, except the most important- Apple seems to be using it more for real apps. Most Objective-C apps are more responsive and could easily provide most of the Java advantages without fuss, if only the API were supported on other platforms.
I hope 10.3.2 fixes some of the little annoyances in 10.3/10.3.1. I gave my iBook to my girlfriend (switched to a PDA as my main machine) a few months back and haven’t experienced OS X 10.3 too much myself, but from what it sounds like there are a lot of small, but very annoying things.
Given that Swing is pretty much native on OS X, you really sure equivalent Objective-C applications are more responsive than Java apps?
The reason I’m asking is because the only Java apps i run on OS X are Netbeans, and it runs slightly faster on my Powerbook 12′ than it does on my work P4 1.8 Ghz.
> Most Objective-C apps are more responsive and could easily provide most of the Java advantages without fuss, if only the API were supported on other platforms.
I’ve seen it running on windows…a few years ago. What was it called…blue box, yellow box or red box. They ditched it. Pity.
You’re right, although it does go a bit beyond that. The UI elements (well, at least 2D UI – the Java3D stuff is still experimental) are hardware accelerated in Panther by default, and you can turn on HW acceleration in Jaguar a couple of different ways. ‘S why Apple is pushing Java development hard on OS X – you get hardware accelerated UI graphics for free. At the World Wide Developer’s Conference in 2002, the Java team was proud of the fact that Java UI elements/GUIs, coded correctly, are the fastest on OS X
It’s almost seems to me that Apple is pushing Java more than SUN … what a pitty
Heh. A pity in what way? Because Sun isn’t eating their own dogfood, or because Apple shouldn’t be pushing Java, as Java isn’t good enough? (the second isn’t my opinion per se, but just one way the statement could be interepreted) It is a pity to me in a couple ways, but generally a good thing. Sun pours millions and millions of dollars into Java marketing, even if they don’t use it themselves much. They certainly are pushing it more than Apple in most ways, except the most important- Apple seems to be using it more for real apps. Most Objective-C apps are more responsive and could easily provide most of the Java advantages without fuss, if only the API were supported on other platforms.
I hope 10.3.2 fixes some of the little annoyances in 10.3/10.3.1. I gave my iBook to my girlfriend (switched to a PDA as my main machine) a few months back and haven’t experienced OS X 10.3 too much myself, but from what it sounds like there are a lot of small, but very annoying things.
Given that Swing is pretty much native on OS X, you really sure equivalent Objective-C applications are more responsive than Java apps?
The reason I’m asking is because the only Java apps i run on OS X are Netbeans, and it runs slightly faster on my Powerbook 12′ than it does on my work P4 1.8 Ghz.
> Given that Swing is pretty much native on OS X
I’m a little confused on your comment of _native_.
Adding the single line of code:
UIManager.getSystemLookAndFeelClassName();
To your JFrame doesn’t make Swing _native_ on OS X. See the below URL for more info:
http://java.sun.com/jfc
There are a few others which one can use which makes the application use the “big-friggin-desktop-menu-at-the-top” and other Apple-ish features.
> Most Objective-C apps are more responsive and could easily provide most of the Java advantages without fuss, if only the API were supported on other platforms.
I’ve seen it running on windows…a few years ago. What was it called…blue box, yellow box or red box. They ditched it. Pity.
I’m a little confused on your comment of _native_.
Adding the single line of code:
UIManager.getSystemLookAndFeelClassName();
To your JFrame doesn’t make Swing _native_ on OS X. See the below URL for more info: