Nick Hanan goes over some of the intricate details of how operator precedence and associativity work when adding custom operators in Swift. I'm still a bit hesitant on operator overloading which was the subject of Nick's previous article. However, if used carefully they can really increase the readability of your code.
What a great idea from Bryan Irace! With all of the ground work Apple has done with extensions in iOS 8 of allowing apps to securely present a view controller in another app this seems entirely possible. It feels like every app that has an in-app browser has implemented it ever so slightly different. It would be great to have that consistent Safari feel and this would make that easy.
Now that we can pass data from the watch to an iOS app this library might seem less necessary but it still has a place. This library enables JSON message passing between app and extension as well as supporting realtime change notifications. There's an excellent demo on the Github page. There's also a good discussion on the Apple Developer Forums of where this library fits in terms of communication between an app and a WatchKit extension.
Norbert Lindenberg gives us a good overview of the pitfalls with developing a custom keyboard for iOS 8. Some very interesting edge cases are covered in this article such as the fact that you can't create a keyboard for only the iPhone or iPad, it must be universal. Restricting the parent app to iPhone for example will still allow the keyboard to be installed when running the iPhone app on the iPad. Worth a read just to see what goes on when developing third party keyboards.
This article from Tim Ekl explains how the compiler feature of designated initialisers added to LLVM has worked its way into Objective-C and Swift. It's interesting that with Objective-C you need to opt into using designated initialisers and, in a way, with Swift it's been flipped and you need to opt out. Tim does an excellent job of explaining so it's well worth a read.