Mailing Lists: Apple Mailing Lists
Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ObjC vs Java -- NEWBIE

Nice list of answers on this thread. For Ryan's specific situation, it boils down to :

Does Ryan want to learn Objective-C ? Does he have the time to do so ?

In all other respects, with a small attention to some UI detail, he might actually do well to just use Java, going to Cocoa-Java only if he finds issues with some Swing control or performance issue, depending on the requirements of his application.

The answers seem to be

1. Not enough to worry about.

2, 3, 4... not a significant difference in either.

5. Aqua look of 1.4+ Java apps is pretty darn good, with the exception of sheets and a few other details which the vast majority of users will never notice, and more importantly, won't care about.

6. You're going to be developing under OS X for *years*, you say? Maybe you shouldn't bother for this project, if you have a serious deadline, but really, why not at least *learn* to develop in the 'native' OS X development environment?

Of course, you say 'a Mac and M$ platform', so maybe cross-platform is key to you... in which case I'd have to ask, why would you even ask the question, given that you're already an experienced Java developer ? If you have no experience with C or Objective-C ( both of which have platform-dependent library issues ) or other cross-platform environments, why *not* use Java if cross-platform is important ?

Ryan's biggest problem with Objective-C is going to be that he's not an experienced C programmer. For him, the most difficult parts of Objective-C are likely to actually be C, once he wraps his head around the Smalltalk-like method syntax.

On Feb 5, 2004, at 4:38 AM, Lotsa Cabo wrote:

(Sorry for cross-posting this. After I sent it to the Cocoa list, I realized that it has equal value being sent to the Java folks.)

I'm still watching the WWDC videos. Since they are on loan from someone, I am trying to go through them before I start writing code. As some of you know, I'm about to write my first Mac application after having been a M$ guy for a few decades.

The app is a simple compiled app that accesses web services from a .NET server, modifies XML files locally, and uploads the XML blobs. I am most familiar with Java, VB, VB.NET, and C#. The most natural type of project for me would be a Cocoa-Java app. Unfortunately, I'm worried about the deployability and speed of the app.

And the questions begin...

1. If I code my Cocoa app using Java, how much slower than Objective-C will Java be?

2. For the .NET WebService access, which is better, Java or ObjC?

3. For XML parsing, which is better, Java or ObjC?

4. Each time I have installed an app on my new PowerBook, I've had to copy one object (I think it's a "bundle") from a drive image to my Applications directory. I think this is a great install process. If I code my app using Java, will I be able to use this type of install method when my app is distributed?

5. Java apps on Windows are ugly. If I code my app in Java, will the user know that it's Java when it's running?

6. The few lines of Objective-C that I have seen has no resemblance to any language that I'm familiar with. Considering I will be developing on a Mac and M$ platform for years, is there any major benefit to learning Objective-C?

In short, I'm trying to figure out which language to use. Thanks, in advance, for those of you that choose to answer / respond.

Thanx,
Ryan
_______________________________________________
java-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/java-dev
Be sure to read the FAQ http://developer.apple.com/java/faq/ before posting
Do not post admin requests to the list. They will be ignored.
References: 
 >ObjC vs Java -- NEWBIE (From: Lotsa Cabo <email@hidden>)



Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.