3 ms·
I don't use the new concurrency features, as they are one of the main culprits of this mess. (so stick with 5.x) SwiftUI is a wreck, that is still not good fo
by ardit33 1y ago
I don't use the new concurrency features, as they are one of the main culprits of this mess. (so stick with 5.x)
SwiftUI is a wreck, that is still not good for advanced UI and you still have to use UIKit for some parts, and
Taking Objective-C, with DispatchQueue, and some modernization of it, and some new data structures, which it need, was all it was needed to make a good new langue.
It could have been Apple's rival to GoLang, but instead it ended up being hydra/monster with too many pardagimns, and none of them are good.
- Hashex129542 1y ago> but instead it ended up being hydra/monster with too many pardagimns, and none of them are good. So true.
- myHNAccount123 1y ago> SwiftUI is a wreck, that is still not good for advanced UI and you still have to use UIKit for some parts, and Skill issue. *ViewRepresentable exists.
- ardit33 1y agoYou are making my point... if you have to use ViewRepresentable in half of the app, then SwiftUI failed. It was supposed to completely replace UIKit, but now it is just another framework to work with... (makes easy things super easy, but harder/complex things harder). It has some ways to go......
- myHNAccount123 1y agoMany developers have no issue achieving their desired designs with Representable or just swiftui.