One thing I see in discussions of SwiftUI is how it’s “incomplete” compared to UIKit And sure, maybe it could use a few more components. But I think these folks also misunderstand just how cheap it is to build components from scratch to the exact needs of your project. Like:pic.twitter.com/CPALsFdc7J
My assumption is still that there isn't really a conceptual model; that components do what they want when they want. You have to know how two components are implemented to know how they'll interact. Better than cramming many responsibilities into UIKit classes, but not great.
-
-
I dunno man, I shipped a whole app using SwiftUI and none of this was an impediment. The speed of development is worth the black boxiness of the implementation. At least, it was for me
-
Fair enough, and I do believe it's firmer footing than UIKit ever had. I see the frustration, superstition, and cottage industry of bad ideas cropping up on StackOverflow and don't think I'm the only one who will find other things to work on.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.