Re: Java vs Objetive-C
Re: Java vs Objetive-C
- Subject: Re: Java vs Objetive-C
- From: Allan Odgaard <email@hidden>
- Date: Sat, 8 May 2004 17:40:02 +0200
On 8. May 2004, at 12:42, Tony Cate wrote:
A friend of mine is a Java developer. He sent me this link. The person
is claiming that Java has been optimized to the point where itbs
faster than Objective-C. He includes some code examples to support the
claim.
It might have been, but his code examples only show that when you need
to compare the same strings a zillion times, Java is faster (than GCC).
In his example, the bottleneck might be method lookup, and I think
that it's already known that Java can be faster at this (than
ObjectiveC).
He does not benchmark plain code (performing calculations), he does not
benchmark memory management (which is the bottleneck of many
applications), he does not evaluate the cost of all the implicit checks
that Java may add to your code, and he does not consider that since the
method invoked a zillion times doesn't do anything different for each
invocation, the JIT might transform it into something which just
returns the number 3 and thus skip the comparisons.
The whole point of his brantb is that Apple should abandon
Objective-C for a more mainline language.
Then he should put forth some arguments -- if I show you that
std::string is faster than NSString, should Apple then move to C++?
ObjectiveC supports open classes, dynamic typing and informal
protocols. Neither is present in Java, and all is used heavily by the
Cocoa framework and by developers.
Furthermore, ObjectiveC allows us to use C++ in our Cocoa applications.
I do not hope your friend makes a living by making technology decisions
;)
_______________________________________________
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.