• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Why Cocoa-java?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why Cocoa-java?


  • Subject: Re: Why Cocoa-java?
  • From: Ondra Cada <email@hidden>
  • Date: Mon, 22 Apr 2002 14:04:19 +0200

On Monday, April 22, 2002, at 06:48 , Andy Lee wrote:

[I]f you seriously aim to please an OS X audience, then stick with Cocoa -- ideally using Objective-C, but Java should work too.

That reflected more of a language bias than I should probably have expressed. I can imagine fine arguments for preferring Java Cocoa to Objective-C Cocoa. Your priorities might lie with features of Java like garbage collection, the exception mechanism, protection levels on methods,
and static data members, which are all either absent or different in Objective-C.

I stand by my bias toward Cocoa (rather than Swing), but withdraw my bias toward Objective-C (rather than Java).

Actually there is a bias toward ObjC, and quite strong one at that. I must say that I subjectively like ObjC and dislike Java, but -- so far as I can judge from others' postings and experience -- the bias seems to be pretty objective ;). At least, I haven't ever heard of any programmer who would know both languages, and choose Java for a bigger project.

As for particular reasons, just scan archives -- we were in this more than once. Among the most important ones are
- lack of proper class support (no this/super in class methods);
- can't use class methods in interfaces;
- impossibility of object embedding and message forwarding (but for extremely inconvenient NSSelector-anywhere way);
- no polymorphism outside of class/interface inheritance (but for... ditto)
;
- lack of categories;
- very weak String class (if compared with NSString).

More or less the only reason for writing Java/Cocoa apps seems to be "I know Java, I don't know ObjC, and in my life I would write only one simple Mac OS X app, so it is definitely not worth to spend the week(*) to learn ObjC".

(*) presuming you know C, otherwise it might be two weeks.
---
Ondra Cada
OCSoftware: email@hidden http://www.ocs.cz
2K Development: email@hidden http://www.2kdevelopment.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
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.

References: 
 >Re: Why Cocoa-java? (From: Andy Lee <email@hidden>)

  • Prev by Date: Being informed when the window moves
  • Next by Date: Re: Why Cocoa-java?
  • Previous by thread: Re: Why Cocoa-java?
  • Next by thread: Re: Why Cocoa-java?
  • Index(es):
    • Date
    • Thread