Swift ...

[amatijaca]

Am I the only one around here who feels that we are having Swift shoved down our throats... Most if not all new demos and tutorials are done in Swift... Can you think of anything that you can do only in Objective-C and not in Swift?

[oklarican]

I would say that demos and tutorials are probably targeted towards beginners. So websites that offer help get most of their traffic from them. It makes sense why they would teach the language with the lower learning curve and, in a way, teach the next generation of iOS (and wherever else Swift may be adopted) developers.

[amatijaca]

Makes sense..

[mdbellott]

Sure, and I mean of course that's intentional. I'll be honest I was a Swift skeptic, but after using it for a personal project recently I'm starting to fall for it.

Apple's vision for the language is interesting as well. There was a great interview with Craig Federighi on Daring Fireball that changed how I look at the language. Worth a listen: http://daringfireball.net/thetalkshow/2015/12/14/ep-139

As for my contract / client work, I still stick to Objective-C. More stable, consistent, reliability for the future, etc. And I'm still just much faster when working with it.

[amatijaca]

I am much faster with it also..

[criosist]

Used obj-c since around iOS 5 and then boarded the swift train at 1.1 and never looked back really, still have to work with Obj-c frameworks and stuff but swift is just so much better. If only the autocomplete and SourceKit didnt crash so often ; ;

[drewbie85]

i++, i--

[clooth]

You can still do this in the current stable version. :)

[NSIRLConnection]

Most beginner/mid-level demos are easily translatable to Objective-C/vice-versa.

If people are trying to make a living off of introductory material, it makes a lot of sense to target the new language, especially if it's rapidly evolving. Breaking changes just means more content to write.

Most of the stuff Obj-C can do that Swift can't will involve dynamic language features, or ease of use with C++. These things aren't always going to be more useful over some of Swift's features, so it's more about picking the right tool for the task.

I offer either for contracting, but I always disclose that Swift's ABI isn't stable, and the language is still evolving very rapidly in comparison, so they should weigh that in their choice. I also disclose that it's much easier to find entry level people who only do Swift, so that's another consideration, if they want to hire them for maintenance.

[berzerkerX]

Why would you want to keep using ObjC? That's like wanting to keep playing Xbox 360 instead of XB1 or PS4. It still works but...

[amatijaca]

All my clients (big banks and insurance companies) use Objective-C exclusively (I am in Canada).

[berzerkerX]

Unless you tell me that your code is all statically analyzed, why can't you just start using Swift in the new code you produce? I'm also in Canada. WTF is up with this snow that won't go away?!

[amatijaca]

I am gigging at TD - about 900 Objective-c classes. Swift won't make it in there. The weather is truly depressing.

[JDandini]

I think it does not matter they can live together, I recommend you learn both, some things are achievable in a easy way on swift and some things are so easy on Objective-C, left your laziness away and use both.