5 ms·
As far as I know all of Apple's framework code is in Objective-C, and there are two big problems standing in the way of converting it to Swift: AppKit and the l
by frankus 10y ago
As far as I know all of Apple's framework code is in Objective-C, and there are two big problems standing in the way of converting it to Swift: AppKit and the like still has to support 32-bit apps (and it's apparently challenging to back-port that support to Swift) and Swift doesn't yet have ABI stability. (source: the SWIFT ADOPTION AT APPLE section here: http://atp.fm/205-chris-lattner-interview-transcript/ http://atp.fm/205-chris-lattner-interview-transcript/)
- leonatan 10y agoThere are a lot more challenges than just ABI and 32 bit. Swift is not dynamic, lacks many of the features the ObjC runtime provides - so most of Apple's frameworks cannot actually be implemented in the same way with Swift. Basic stuff like KVC, KVO, responder chain, etc. go out of the window. And many of Apple engineers are not convinced throwing these technologies out of the window for some imaginary benefit from Swift is the right direction.