Steve Troughton-SmithDec 30

🗣️ I do enjoy a good rumor, so I'll share this nugget:

I have heard that SwiftUI has been losing political capital, and credibility, internally at Apple because it has repeatedly failed to meet software engineering goals, and needs. It's no longer thought of as clear default choice for new stuff.

That might explain why it was deemphasized at WWDC compared to the past few years.

Comforting that Apple might finally be waking up to the reality of SwiftUI, 6 years in. Glad I waited that one out 😅

Show threadEthanRDoesMCDec 30
@stroughtonsmith for me, SwiftUI solves the Auto-Layout problem (I never could visualize constraints very well) and Observability makes it so I have almost zero edge cases. AppKit and UIKit gained the latter. A Storyboard replacement in the form of some “SwiftUI Layouts” would be welcome, but it’s time to go back, I think. NSImageView is for example so unbelievably performant compared to Image() that it was a no-brainer for my launchpad clone. And we still don’t have cell reuse outside of List (and I’m not really convinced it’s _really_ reusing cells there either)… Time to go back to AppKit and UIKit. But they’ll never give us PepperUI so I guess SwiftUI on watch forever? Or maybe it’s time to trust us, Apple.
Show threadEthanRDoesMC
@stroughtonsmith my experience with SwiftUI can be summarized as such: it takes you 85% of the way there, you’re feeling good, and then the moment you want to make a good product into an excellent product it becomes quickly apparent you should’ve been in UIKit or AppKit the whole time
Dec 30 at 8:27pmWeb
Show threadNathan KingJan 6
@ethanrdoesmc @stroughtonsmith As an experienced developer working on my first Mac and iOS apps, this has been exactly my experience. It’s easy to get something decent up and running, but the pain quickly sets in as you begin to tweak the defaults.