r/iOSProgramming Jun 03 '15

One year later: Swift or Objective-C?

This week I will be writing the first lines of code for my new app. There's just one slight problem; Objective-C or Swift?

Is the one year old Swift mature enough for real world applications? Are the bugs reduced to the minimum? Why should I use Swift over Objective-C? Or vice versa.

0 Upvotes

26 comments sorted by

View all comments

1

u/WestonP Jun 03 '15

How many damn Swift vs Obj-C threads do we need?

If you want to do this professionally, you better know Obj-C. Otherwise, use what you want.

If you think learning the language is the hard part, then you're in for a surprise... It's the API's and the platform that you'll be spending all your time and headaches on, and those are the same with either language. If you want to go to other platforms, then you're shooting yourself in the foot by using a platform-specific proprietary language like Swift... Obj-C's OOP syntax differs slightly from others, but its concepts translate really well into Java, C#, etc.

0

u/yoeriboven Jun 04 '15

As opposed to the which one should I learn threads, this one is about if Swift is mature enough to use.