I'm an ObjC dev and I encourage folks to learn Swift, which I am also doing. The thing about learning Swift and still needing to know UIKit is true - it'd be li

I'm an ObjC dev and I encourage folks to learn Swift, which I am also doing. The thing about learning Swift and still needing to know UIKit is true - it'd be like learning Rails without Ruby, which you just can't do. The first Swift book did a good job introducing you to the language, but didn't delve in to the reality of UIKit at all, which the second book did fill in on. But there are still places where you have to use an NSDictionary over the fancy new Dictionaries, and that reality is very much still here. If I were starting a new project tomorrow, I'd still use ObjC. If someone where working for me, I would encourage them to learn ObjC for now. Swift isn't going anywhere, but neither is ObjC, and the path from zero to app is still easier in old ways I think.