singledatapoint
trozI love writing and using SwiftUI, even though I acknowledge that it isn't perfect. I thought I'd publish some of my thoughts as a rebuttal of some of the recent anti-SwiftUI posts.
Lars Christiansen@troz Thanks for your very welcome contribution to the SwiftUI discussion.
I wholeheartedly agree with you.
Wondering how much of the complaints are due to the « New Shoes Syndrome ». 🙂
I wholeheartedly agree with you.
Wondering how much of the complaints are due to the « New Shoes Syndrome ». 🙂
Lukas Kubanek@thuro @troz I used to jump on every new piece of technology Apple unveiled, and SwiftUI was no exception. No “new shoes” syndrome here. In fact, I’m a big fan of the model, but after spending some time working on a new iOS app, I started running into a lot of limitations and ended up patching underlying UIKit components more and more often. At some point it just became too much, so I figured that with AI, it might make more sense to go UIKit-first and use SwiftUI mainly for leaf views.
Keren R. Bell@troz Really great piece, particularly agree with the Building part of why SwiftUI stands out, I think people miss the forest for the trees there often.
Would you like to have this be part of the Swift Blog Carnival we’re running this month about SwiftUI? I think it’d be great piece to add to the lineup (and balance the takes somewhat 😅 we mostly have complaints rn)
https://swiftcarnival.github.io/
Would you like to have this be part of the Swift Blog Carnival we’re running this month about SwiftUI? I think it’d be great piece to add to the lineup (and balance the takes somewhat 😅 we mostly have complaints rn)
https://swiftcarnival.github.io/
Neil Hargreaves@troz thanks for the interesting perspective. For me a lot of the problems related to transparency. How about a page of what functionalities are not (yet) available in SwiftUI, cases where the developer should expect to mix it with AppKit or UIKit. It's standard corporate behaviour to aim high, but it's led to a lot of alienation. More *consistency* would have been better, to know the ins and outs of just one framework is already a huge mental load.
Puppethead@troz I'm happy to see pro-SwiftUI sentiment expressed. I've felt a lot of "SwiftUI doesn't work" criticism comes from developers who expect things to work a certain way and don't spend the time and effort to explore SwiftUI nuances. Even if a lot of it can be nonsensical, such as the order of modifiers changing behavior.
I was slow to adopt SwiftUI, but am so much more productive now that I have. It's much easier to tinker with possibilities than it is using NIBs or Storyboards *shudder*.
Brett Walker@troz I think I’m in the middle I’m the debate. The declarative nature of SwiftUI is cool, however there’s weird choices, like why does NavigationStack want us to hardcode knowledge of other Views into it? Why is there no reliable lifecycle to listen to? Why do view modifiers with closures exist when we’re supposed to get logic out of the View? Why are UI components different from UIKit? It feels like there’s no guiding hand at work and the framework has way too much “trust me bro” attitude.
Sam Deane