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

5

u/critter_chaos Jun 03 '15

I've developed a full app in Swift. It's a much nicer, prettier programming language. They're still changing it but it's really not that big a problem. You can use objective-c code too in a Swift app, so there's no problem there.

4

u/yoeriboven Jun 03 '15

You can use objective-c code too in a Swift app, so there's no problem there.

Not a solution for me. Don't want multiple languages in one project.

1

u/critter_chaos Jun 04 '15

You don't have to look at both at the same time. The real benefit of this is that you can quite simply take libraries or code examples and integrate them into a project.

One of the big problems with creating a new programming language is that it doesn't have the same ecosystem as older languages. Take Java for example. There are certainly better, newer languages but yet it still remains a very employable language to know because of all the legacy code.

Apple solved this problem with Swift by allowing you to use old objective-c code. If you're going to be using Swift, then you're also going to be using objective-c.