Re: Native Cocoa vs Java performance question
Re: Native Cocoa vs Java performance question
- Subject: Re: Native Cocoa vs Java performance question
- From: Jeff LaMarche <email@hidden>
- Date: Sat, 5 Apr 2003 23:47:04 -0500
On Saturday, April 5, 2003, at 08:55 PM, Bill Bumgarner wrote:
Yes. You are doing something really bad. ;-)
Java will always win in this case, but the test is largely irrelevant.
Another point that Bill didn't make is that when it comes time to
optimize performance (and IMHO it sounds like you're way too early in
development to be doing any optimizing whatsoever), Objective-C
provides you with a lot more flexibility. Being a superset of C, you
have the ability to get right down to the metal if you need to in order
to optimize your performance - you can use pointers and alloc/malloc or
even put assembly code in if you really want to. You have far more ways
to optimize in Cocoa.
However, nowadays it's rarely necessary to get all the way down to the
metal unless you're doing something extreme like writing a
ground-breaking game or 3D package, in which case you shouldn't be
using Java anyway.
In the long run, well-written Objective-C code is musch easier to
maintain and less complex to understand than well-written Java, and
from the user's perspective, the interface will likelybe snappier.
You'll also spend less time writing and maintaining your code, which
will leave you more time later to worry about eeking out extra seconds
on some of your algorithms.
Jeff
(and if you think I'm biased, I am, but it's not for lack of knowledge
- I spend probably 85-90% of my professional life right now fighting
with Java; I program in Objective-C mostly on my own time for the sheer
joy of it - it's relaxing and downright fun.)
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.