Swift seems great, but I wouldn't expect any huge technical advantages over Obj-C until Apple stops caring about Obj-C (which I suspect huge chunks of Cocoa are written in for starters).
http://www.h4labs.com/dev/ios/swift.html
Apple is doing a good job of updating ObjC but Swift already has the momentum. Apple has made it clear that they want Swift:
http://ericasadun.com/2015/04/14/swift-in-case-you-didnt-thi...
You can choose to ignore their subtle messages (e.g. use Autolayout, Size Classes) but at some point in the not too distant future, you'll likely regret not starting with Swift earlier.
I was just pointing out that the original linked article isn't really about Swift, just an Apple framework that can be used with Swift.
So -- going back to the original point -- in fact this was Swift catching up with Obj-C, so it does pertain to Swift but is not evidence of Swift getting ahead of Obj-C.
The message is clear: learn Swift or be left behind.
I paid great attention to both WWDCs. In fact I read the Swift book immediately after the announcement. However, the point I am making remains true: Obj-C isn't going away soon and the linked article is not about Swift pulling away from Obj-C (indeed, it's about Swift catching up to Obj-C -- see author's comment elsewhere in thread).
In fact, here's a link to an article explaining how to bridge from Swift to Obj-C to make use of simd.h.
https://www.safaribooksonline.com/library/view/learning-swif...