On Jun 7, 2008, at 9:01 PM, Felipe Monteiro de Carvalho wrote:
On Sat, Jun 7, 2008 at 11:38 AM, Jose Raul Capablanca <[EMAIL PROTECTED]
> wrote:
With the exception of the id and SEL types,
categories, and the fact that you can send messages to nil, I can't
think of
anything in Obj-C that isn't done better in Java,
Here is one: Integration with other languages
Java's integration with other languages (as using Java libraries in
other languages) is about one of the worse I've ever seen. It
basically makes any Java library accessible to only Java.
That's not really relevant to the point I was trying to make. Besides,
how good is Obj-C's integration with other languages in the same sense
you're referring to above? Can Obj-C libraries be used in other
languages? I don't think so.
And a second one: Performance
Again, that's irrelevant, since OS X applications aren't cross-
platform. Java applications built to run only on Macs can be compiled
natively. Moreover, a performance argument can also be made against
Ruby and Python and, yet, there *are* Cocoa bridges for those languages.
If people are going to ditch Java as a contender for a native language
for Cocoa (in a parallel universe, of course), they should do it for
the right technical reasons (in addition to the right non-technical
ones). As Michael Ash pointed out, Java's object model is not
perfectly matched with Cocoa's, and that's a reasonable argument.
I still don't see any good-enough *technical* reason to justify basing
Cocoa on an extension of C, however. That's all I've been trying to say.
Wagner
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
