3 ms·
Anecdotal, but it seems to be on par with iOS Objc->Swift. New stuff is Kotlin, but unless you have a strong reason to rewrite, it stays ObjC.
by voz_ 6y ago
Anecdotal, but it seems to be on par with iOS Objc->Swift. New stuff is Kotlin, but unless you have a strong reason to rewrite, it stays ObjC.
- complexworld 6y agoA major difference is that there is a tool for automatically converting from Java to Kotlin. I don't think that exists for Objc to Swift.
- krrrh 6y agoThere is this, which can help get started. http://swiftify.com/ http://swiftify.com/
- V-2 6y agoThe code it generates leaves a lot to be desired. It's highly non-idiomatic, and has the marks of a computer-generated structure all over it. This being said, it certainly facilitates the transition from Java to Kotlin as it makes for a convenient learning tool (used on small portions of code).
- melling 6y agoThe transition to Swift has accelerated in the past year. Might be because of SwiftUI or because it’s now mature. https://www.tiobe.com/tiobe-index/ https://www.tiobe.com/tiobe-index/
- dep_b 6y agoABI stability. You don't need to ship the whole runtime with it anymore. Though if you want a framework that works nice with both languages and older versions Objective-C is still better.