As someone who's done iOS development for major corporate, financial and banking applications for about seven years now, I'd have to say that a) I understand UIKit fairly well, and b) I'm not so sure it's "loved" by many. ;)

Like I pointed out in the article, UIKit does indeed have "years and years" of development behind it... and it shows. UIKit applications are a haphazard mishmash of techniques, technologies, and design patterns dating back decades.(Yep, plural, since delegates and KVO are patterns based in AppKit.)

Besides, the article reiterates what Apple clearly demonstrated during WWDC. Want do do new widgets? SwiftUI. App Clips? SwiftUI. New Watch complications? SwiftUI. New Catalyst cross-platofrm applications? SwiftUI.

It's still not possible to do everything an app may need to do in SwiftUI. The iOS SDK is too vast for that.

But I strongly suspect that people had much the same sentiments when Apple migrated from Carbon to Cocoa, and I know that when Swift first appeared people felt much the same about moving away from Objective-C. “Swift? Yeah, it may be the future, but they’ll always be a place for Objective-C.”

Except that, today, there isn’t a place for it, as all of the new features mentioned above are impossible to implement in Objective-C.

And because of that, I also believe that the future is going to arrive faster than anyone may think today...

Thanks for reading and the comments.