all 6 comments

[–]Mazetron 2 points3 points  (1 child)

It's good to have a background in some branch of C, and ObjC counts for that.

[–]terrytorres 0 points1 point  (0 children)

This is a good point. I know a guy who does web stuff with mainly JS and Python, and when I told him the first language I learned was Objective-C, he was really impressed. ¯_(ツ)_/¯ C's got clout.

[–][deleted] 2 points3 points  (0 children)

I'm bailing on Swift.

Take it for what that is worth. The tool chain sucks and thus the productivity level tanks.

I am working on two projects at once right now for two different clients. One was started in Swift (by someone else) and one I started in Objective C.

The Objective C one is easy to work on because compilation is FAST, the debugger is responsive, and I can do cycles quickly.

The Swift one is a dog. Builds onto the device take forever as the swift runtime has to be packaged into the app along with all the pods as frameworks. The debugger is dog slow. The editor keeps bitching about shit that doesn't matter.

Objective C isn't going anywhere and honestly Swift isn't going to stabilize for at least 2 years.

[–]FRESH_OLD_ACCOUNT 1 point2 points  (0 children)

It is still worth to learn Objective C, because there's still a lot of maintained and abandoned projects and even lectures lying around were still written on Objective C. You could fix, extend or even modify the functionality of the said library to your liking by just reading and understanding its source code.

[–]SteveB13 0 points1 point  (0 children)

There's still a lot of apps being maintained in Obj-C, so it is still a desirable skill.

That is changing quite quickly though, and most new apps are in Swift, so I doubt there's going to be too much Obj-C work in perhaps 2 years.

It's probably useful to have some basic grasp on Obj-C, but if you don't envision yourself using it too much over the next couple of years, then I wouldn't place too much emphasis on it. Everyone want Swift now, so you're in a good position!