It's Coming: the Great Swift API Transformation

Ever since before Swift was released, there’s been a style gap between Cocoa interfaces and APIs in the Swift standard library; lots of things just look different, often needlessly so. This is no mere aesthetic concern; non-uniformity and lack of predictability make everything harder, from coding to debugging to maintenance. Fortunately Swift developers created tons of great code in spite of that gap, and along the way, there evolved a sense of what “Swifty” code looks and feels like.

→ swift.org/blog/swift-api-transformation/

Apple saw a style gap between Cocoa interfaces and the Swift standard library. This gap made coding, debugging, and upkeep harder. To fix it, they made new API design guidelines based on what feels right in Swift. They used these guidelines on the standard library and how Objective-C APIs come into Swift. They showed examples of changes and asked the community to review and suggest improvements by February 5.