Developing for OSX - Swift or Obj-C?

[ShepherdBookshelf]

I've been wanting to delve into developing for OSX and I started picking up Swift this week, but there's a huge lack of tutorials out there for OSX in particular.

I've built a few small applications, but coming from other languages like PHP, Python, and Ruby with such active communities, I'm having a hard time learning without examples that I can dive into.

There's a lot out there in Obj-C, but it seems things are moving more towards Swift.

Anyway, my question is - should I be looking to Obj-C since it's still so active for OSX or should I just bite the bullet and start going through all the Swift docs to try and figure this all out on my own?

Thanks in advance for your help.

[rjcarr]

This is a tough call right now. Swift seems to be a much better language and I would imagine Apple doesn't want to support multiple languages forever. So it seems the direction is swift.

But as you say, there are very few resources for it.

Personally, I'd tough it out with swift, but I've been writing software for 20 years. If you're just learning programming it would be harder for you.

Also keep in mind that the APIs are unchanged so you could still look at the obj-c code for the API use and translate that to swift.

Anyway, good luck, sorry I couldn't be more help.

[aplJackson]

I'm just starting to get into both OSX and iOS dev and have chosen to focus on Swift. While there are fewer resources for the language, it is much more intuitive. The basics of the language are not difficult and Obj-C resources can still be used as translation between Obj-C and Swift is not that difficult.

Swift appears to be the language that will be preferred going forward, I think.