Should I learn PyObjC or just dive right into Objective C?

Nerd. :)

Do you want to develop for the iPhone?
@chyna that nerd probably wrote a program you’re using right now.

No doubt! I’m just jealous.

@styfle In the future, yes, but now I’m just trying to have a little fun learning something new—I was inspired by a question on here the other day.

I’m a newbie C/C++ programming and after watching the Stanford objC class, I still don’t get it. I’m not used to working with a GUI or having to use a base class for stuff. I just know how to write stuff that runs in console/terminal. You sound like you know what you’re doing so I would just go for it. What exactly is pyObjC anyway?

The actual amount of working with pointers and handles that you do in idiomatic Objective-C is minimal. (Yes, each object is really a pointer, but you’re treating it semantically as an object and not as a pointer.) Most of Apple’s documentation is written assuming Objective-C as an implementation language, and so you’re going to need to learn enough of it to translate anyway, so you might as well start there.

If it doesn’t work out for you after you’ve spent a week or so at it, much of the stuff you learn about Cocoa will transfer directly to PyObjC, so it’s not like it will be wasted effort.

I may end up doing it in straight Obj-C anyway since I can’t get PyObjC to compile.

@styfle
> What exactly is pyObjC anyway? <
Google’s a great search engine. :)

Here’s your answer.

@archaeopteryx I was on my phone and didn’t feel like searching it at the time, but thanks for the info. I still think you should just go Obj-C, andrew.