6 ms·
It highlights some of challenges of bridging Swift with ObjC APIs.
by millstone 7y ago
It highlights some of challenges of bridging Swift with ObjC APIs.
- kitsunesoba 7y agoFully Swifty UIKit or whatever it is that eventually replaces UIKit can’t come soon enough. As Swift has matured, UIKit/AppKit has quickly become the weakest link in the Apple platform dev experience.
- millstone 7y agoYes, which Apple has done with some success (Toolbox -> Carbon -> Cocoa) but we've also seen how WPF, etc have gone down. The hard challenge is the migration path, and you can't commit until the language and tooling is ready.