3 ms·
Forever. It's much easier when you deal with low level code from Objective-C(++) and Apple has tons of that written with no obvious benefit when it's rewritten
by dep_b 9y ago
Forever. It's much easier when you deal with low level code from Objective-C(++) and Apple has tons of that written with no obvious benefit when it's rewritten in Swift.
They might introduce modules that are incompatible or awkward to use with Objective-C in the future though.
- pjmlp 9y agoThe benefit are dogfooding and public image. Microsoft already did it multiple times when VS team had to adopt WPF, the new APIs that are COM only or latest example having the Office team adopt the desktop bridge and make it a UWP only application on Windows 10. If anything, to give the message to the world that the internal teams also use the technology they are trying to sell. And they are slowly doing it, given that launchd and the Dock were rewriten in Swift for Sierra and the new XCode 9 build system is now in Swift, as well as some parts of the Store app.
- dep_b 9y agoYeah I remember people being really sceptic in the beginning that Apple wouldn't even use Swift for it's own projects. People pretending to have "inside knowledge" nobody uses Swift at Apple internally, claims like that. You have to silence those critics.