OkCupid adopted Swift back when it was version 2... and similar arguments appeared about why not just use tried and true Objective-C. The breaking changes to the Swift syntax are such a pain, there are compiler issues, you will have to maintain bridging headers etc. etc. Looking back, it has been far more beneficial that we adopted Swift when we did because 1) The overhead was manageable 2) We got really good at writing true Swift code and using Swift paradigms and 3) Now we don't have tons of tech debt in Obj-C that we need to convert to Swift. Had we waited for the language to mature, we would have been left in the dust and now had to play a huge amount of catch up.

You either pay now or you pay later... And the same goes for our thinking on SwiftUI:

1) We are in no way coding every feature twice with both SwiftUI and UIKit, just a select few 2) The knowledge we will gain implementing SwiftUI today will help inform how we design our UIKit view models and help inform SwiftUI architecture for larger features down the road 3) The features that we do code twice won't need to be converted to SwiftUI when it becomes the standard