[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Apple should get behind Cocoa Java

Subject: Re: Apple should get behind Cocoa Java
From: Charles Miller <email@hidden>
Date: Wed, 16 Aug 2006 09:48:45 -0700
Delivered-to: email@hidden
Delivered-to: email@hidden

On 16/08/2006, at 9:06 AM, Shawn Erickson wrote:

If you note various other Objective-C language bridges are mostly
maintain by a community of folks outside of Apple with Apple
leveraging that work by including aspect in developer tools and/or
operating system.

I suspect the other bridges are a lot easier to maintain, since they tend to use dynamic typing and features like Ruby's method_missing() to save them having to generate static types up-front for all the bridged Objective-C classes. From what I could see, maintaining the CocoaJava API required a lot of manual translation of Cocoa concepts (for example, informal protocols) into Java types and idioms.

C
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden

This email sent to email@hidden

References:
	>Apple should get behind Cocoa Java (From: Vince Marco <email@hidden>)
	>Re: Apple should get behind Cocoa Java (From: "Shawn Erickson" <email@hidden>)

Prev by Date: Re: Columnheads of JTable become 'blue' (like they are selected)
Next by Date: Re: Apple should get behind Cocoa Java
Previous by thread: Re: Apple should get behind Cocoa Java
Next by thread: Re: *We* should get behind Cocoa Java
Index(es):
- Date
- Thread

Home