One huge reason to use C++ on iOS is to avoid platform lock-in and for code sharing. How can you miss such a blindingly obvious reason?
And it is right on par with other languages when it comes to GUI building as Qt proves. However, something like QML in conjunction with C++ will be much more flexible and pleasant to use than any of C++, Objective-C or Swift.
CoreData is widely considered to be more trouble than it's worth it, as soon as you want to do some serious work. Predicate filtering... maybe I am missing something, but I'd pick <algorithm> + lambdas any day over that kind of magic.
I have used Objective-C to write production code, and with few exceptions, I would consider it anything but elegant. It's a hodge podge of concepts thrown on top of eachother that's finally and deservedly being put to rest by Apple.
And it is right on par with other languages when it comes to GUI building as Qt proves. However, something like QML in conjunction with C++ will be much more flexible and pleasant to use than any of C++, Objective-C or Swift.
CoreData is widely considered to be more trouble than it's worth it, as soon as you want to do some serious work. Predicate filtering... maybe I am missing something, but I'd pick <algorithm> + lambdas any day over that kind of magic. I have used Objective-C to write production code, and with few exceptions, I would consider it anything but elegant. It's a hodge podge of concepts thrown on top of eachother that's finally and deservedly being put to rest by Apple.