SwiftUI is not ready just as Swift itself wasn't ready for production apps until 3.0 (maybe 2 if your team was particularly fond of constant refactoring).
Stick with RxSwift MVVM/MVP if you want reactive functional programming.
Stick with RxSwift MVVM/MVP if you want reactive functional programming.
I overheard someone once say they used NotificationCenter as the data binding mechanism in an MVVM app. Big Yikes.
Another pain point IMO is the uncertainty of not knowing Apple's plans and timelines. For example, why did Apple take so long to release ABI stability for Swift? When will ObjC be finally deprecated? Is SwiftUI going to replace UIKit and Cocoa? If yes, when will that happen? Is it worth it to invest serious dev time into a new macOS Cocoa product if SwiftUI or even Catalyst will be the de facto option in, say, 3 years?
iOS devs seem to be happy rewriting their products every year after WWDC and chasing after Apple's decisions which doesn't really seem a sustainable business model.