Re: Mixing Cocoa and Cocoa-Java
Re: Mixing Cocoa and Cocoa-Java
- Subject: Re: Mixing Cocoa and Cocoa-Java
- From: Scott Ellsworth <email@hidden>
- Date: Mon, 6 Mar 2006 15:08:17 -0800
Gah - hit send too early:
On Mar 6, 2006, at 2:58 PM, Scott Ellsworth wrote:
Further, the JVM has gotten quite good on MacOS X, especially if
you are not using Java graphics, so it is not a bad way to use
special purpose libraries like Accelerate.
Which should have said
it is not a bad way to use special purpose libraries, like JMS
systems, general database access systems, or any other setup with a
mature Java library.
That mature library might also call across JNI back into C. Again,
as long as the operations take substantial time, this can still be a
win. I had a system solver that used LAPACK, where each solver step
took a second or so. Each step was composed of twenty calls into a
50ms set of LAPACK calls, which went faster when I let Accelerate do
the heavy lifting.
I might have taken the time to rewrite the whole middle layer into C+
+, but that time was better spent on a decent front end, because I
knew that the solver worked. It also had a mature fallback library
for use when there was no native lib to call into, so I had little
motivation to rewrite it.
In summary, Java can be called from Cocoa without an impactful
performance penalty, as long as the conditions are suited to it.
Don't optimize early, but make sure performance is good enough, and
you should be fine.
Cocoa/Java, on the other hand, is discouraged by Apple, and they are
not going to move new Cocoa functionality into Cocoa/Java.
Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden