3 ms·
Yup... I liked the old one much better. My guess, over time, they will fix the issues, but that's the typical hickups of a framework that is still too immatur
by ardit33 3y ago
Yup... I liked the old one much better.
My guess, over time, they will fix the issues, but that's the typical hickups of a framework that is still too immature.
It took Swift (the language) about 6-7 years to mature up. I think the language became 'mature' only around version 5.5. Whoever used it earlier, got to hit all kinds of weird issues and instabilities.
SwiftUI, will have a similar arch. My opinion is that it is about 2-3 years to be mature enough, to replace UIKit altogether.
- novok 3y agoIn iOS 2 UIKit was far more 'mature' of a framework than SwiftUI was, and it wasn't full of missing stair steps like basic navigation pushes working without it being a whole irritating song and dance, lazy loading table cells & navigation views, being able to hide the tab bar when you push a screen on one tab with things like "hidesBottomBarWhenPushed", etc. Overall I think SwiftUI when released, and even today in some corners, is a general overall theme of incompleteness with features available in iOS 2's UIKit. Did early iOS have it's irritating parts? For sure, but they were there for performance reasons mostly and it wasn't an 'incomplete' framework like SwiftUI is.
- cvwright 3y agoOverall I really like SwiftUI. As a total iOS newbie when it was new, I don’t think I would have bothered if the only option was to slog through UIKit. But all the complaints about its incompleteness are spot-on. How did they think it was ok to launch without basic stuff like NavigationStack? Standard Apple “piss on my head and tell me it’s raining”.