3 ms·
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). Stic
by 5cott0 7y ago
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.
- pier25 7y agoSadly SwiftUI is a beta like Swift was back then. 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.
- kitsunesoba 7y agoAs a counterpoint, if your app hasn’t moved to a reactive functional setup already, it may be worth holding off and waiting for SwiftUI and Combine to mature, because architectural libraries are pervasive and can be incredibly difficult to remove or migrate away from.
- 5cott0 7y agoRxSwift is just an implementation of Rx (Observable pattern) and doesn't really qualify as an architectural library and MVVM/MVP with proper separation of concerns should not be difficult to refactor to use another data binding pattern. I overheard someone once say they used NotificationCenter as the data binding mechanism in an MVVM app. Big Yikes.