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

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

Perhaps some. Overall this should be farely negligible. Unless you're doing
something where performance is a huge requirement and you're going to be
tweaking for every last possible millisecond of speed, I doubt anyone will
notice.

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

Both Java and Objective-C have good WebService libraries. Either are going to
let you get the job done. I would say that Java's WSDP has a large install
base and might be more mature, but Apple's WebServicesCore is great as well.

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

Faster? Easier to use? I would again say things are pretty comporable. Once
again I would tend to lend towards Java's Xerces/Xalan XML parsers for their
maturity.

> 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?

Yes. There are multiple ways of turning a Java application into a bundle and
placing it into a dmg.

> 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?

Maybe. The Aqua L&F for Java is pretty good. If you pay attention to the user
interface details that are specific to the Mac environment than most users
won't know or care. There are a few details in a Java apps that can give them
away, but for the most part it doesn't matter.

> 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?

Well, this is a Java list, so I'll give you a biased answer. Objective-C is
only useful if you want to do some very tight integration with MacOS for things
like AppleScript integration, mucking around with the Dock Icon while the
program is running, etc. It's not that there aren't ways to do it in Java,
it'll just take a lot of work. In terms of "bang for you buck," become and
"expert" in Java presents more opportunities on more platforms.

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

Like I said, this is a Java list, so most people's opinions will probably lean
toward Java. I always lean towards Java first unless there's a good reason not
to.

-jdr


Jordan Reed | http://www.chaosserver.net | http://carbon.sf.net
_______________________________________________
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.