• 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: Cocoa Java futures, NDA's etc
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cocoa Java futures, NDA's etc


  • Subject: Re: Cocoa Java futures, NDA's etc
  • From: Brian Hannan <email@hidden>
  • Date: Wed, 27 Oct 2004 11:54:16 -0700

On Oct 27, 2004, at 3:43 AM, Finlay Dobbie wrote:

Considering Tiger isn't even going to be out until some way into next
year, how long can you wait until targetting it?

Right. If I was planning to have a Tiger app rolling the day Tiger was released, I'd fork out the cash. I'm more concerned right now on whether Apple will do what it appears to be thinking, shoving Cocoa-Java into legacy.

Considering all the "big" apps from third parties I see -- MS Office, Adobe Creative Suite -- are Carbon anyway. And people building MacOS X specific apps with lots of OpenStep history/legacy code -- or from scratch -- are happy with learning Objective-C, so much the less it is for Cocoa-Java.

The Java Bridge certainly seems to have been created because Apple (or
more likely NeXT) suddenly got this idea that WebObjects had to be
Java to make it more marketable to the enterprise crowd.

I do remember Apple mentioning, I and believe delaying 10.0, because they wanted to make sure App Kit and Foundation were available in Java. Thinking app developers would be terrified of learning Objective-C. That didn't happen.

Anyway, my considered opinion based on publicly available information
is that the Java bridge isn't worth pursuing.

The terror of it all is if you have a back-end entirely in Java and want to give a MacOS X user the best UI experience, Cocoa-Java was great way to do it. I've got Swing client versions for Windows/Linux in dev, since Swing is designed to look best on Windows anyways. With no Java bridge, forget the extra effort. It's Swing for MacOS X as well. Too bad.

--
Brian Hannan
Chief Admiral of Uncle Jam's Navy

"One nation under a groove, gettin' down just for the FUNK of it."

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
  • Follow-Ups:
    • Re: Cocoa Java futures, NDA's etc
      • From: Finlay Dobbie <email@hidden>
References: 
 >Re: Cocoa Java futures, NDA's etc (From: jason rusoff <email@hidden>)
 >Re: Cocoa Java futures, NDA's etc (From: Brian Hannan <email@hidden>)
 >Re: Cocoa Java futures, NDA's etc (From: Finlay Dobbie <email@hidden>)

  • Prev by Date: NSTimer not getting called with "shared" object
  • Next by Date: Populate a NSPopupButton with ascii
  • Previous by thread: Re: Cocoa Java futures, NDA's etc
  • Next by thread: Re: Cocoa Java futures, NDA's etc
  • Index(es):
    • Date
    • Thread