I think what I wrote was misleading. When I wrote that I never migrated to Swift, what I meant was that I never bothered learning it. It broke my heart to have to work on iOS and throw away my Objective-C knowledge and trade (the UI stuff of ) UIKit for SwiftUI, especially as all that remained a moving target for a long time.

I just went and got a new job. I'm doing web front-end work with React and TypeScript. I'm not crazy about that, believe me.

I don't even bother with iOS stuff right now as a hobby, because I can't really stomach it. I really think Apple went the wrong way.

On a side note, I can't stand "reactive" UI's (though that's what I work with now). You know, key-value coding and notifications on iOS can be used to make a reactive UI (of sorts), instead of updating the UI imperatively. But all the books I've ever read from iOS people who knew what they were talking about always warned strongly about overusing KVC or notifications: specifically, because it makes reasoning about how code works more difficult.

So, what the hell then is the idea of a reactive UI. It's taking the kind of architecture or pattern programmers have always been warned not to use, and then turning the entire UI into that!

I am really just down on the whole thing. I think it's a mistake.