🗣️ 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 😅
This one is getting traction again lately, so I'll add some fun bits of context. Apply salt *liberally*
• I've heard Swift is also under fire from certain corners at Apple, lumped in with SwiftUI — many frameworks built atop it just aren't working to a standard people are happy with, it's dramatically increased the resources and time required to build the OS, and it does not work well enough at the OS and kernel level in embedded or secure contexts
• Paraphrased: 'Even Tim knows SwiftUI sucks'
@apple4ever @kalleboo @stroughtonsmith Is there a dev path that best supports ai-coding?
If there is then they will choose that.
Steve Troughton-Smith
Karl Baron
Matt
John Gordon