Re: Java vs Objetive-C
Re: Java vs Objetive-C
- Subject: Re: Java vs Objetive-C
- From: Bob Ippolito <email@hidden>
- Date: Sat, 8 May 2004 14:13:19 -0400
On May 8, 2004, at 11:40 AM, Allan Odgaard wrote:
On 8. May 2004, at 12:42, Tony Cate wrote:
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 ;)
Amen. One of the best things about Objective C is that the runtime is
so dead simple that it's easy to understand and interface with.
Because of this, Objective C is rather seamlessly bridged with many
languages including C/C++ (objc_msgSend), Java, Python (PyObjC), Io,
F-Script, Ruby, Perl, AppleScript, etc. If it doesn't already talk to
your favorite language/runtime, then (assuming adequate skill and
patience) you can also write a bridge.
If you want something that Objective C doesn't do, or doesn't do well,
then just use another language -- even Java. You don't need to replace
Objective C, just augment it.
-bob
_______________________________________________
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.