macOS Cocoa: Java or Objective-C?

[Josh]

I'm going through a C++ course now, and I have a good book on C, so I am slightly familiar with that.

I want to learn ObjC really, really badly, and I plan to once I feel very comfortable with C++. I'm mildly comfortable with some things, but I'm not moving on until I feel very confident in the language.

Then I plan on to go through the C book I've got again, then on to ObjC, then Cocoa.

Mac/Cocoa developing is something I absolutely want to do so badly that I doubt I could explain it

 

[HiRez]

not to say objc sucks, i'm plodding through the kochan and hillegass books, and i'm liking it so far just, sorta useless when it comes to most of the stuff I end up doing in school and outside of class (where java and C++ tend to be more popular)

Kind of, but one thing that I will say is that if you're doing a lot of Objective-C, you'll also be doing a lot of straight C as well, and that's probably a good thing. There's still a lot of APIs that aren't wrapped for Cocoa, and even while using Cocoa you use a lot of C. And C skills can be put to use in lots of places (and much of Java is based on C as well).

 

[Catfish_Man]

Of course, that's true. I've never suggested to anyone to bother with the Cocoa-Java bridge. It was a quick-and-dirty thing to allow people who didn't understand Objective-C to get by.

Also, we're using it in Adium 1.0 to bridge to a Java library.