Hacker News Reader

I really wonder where this is going.

Swift had to interop with objective-c right from the start, which itself had to interop with C. SwiftUI feels like a wrapper over UIKit (or at the minimum CoreFoundation).

All in all, it seems impossible that so many layers of compromise over so many years, can lead to anything clean in the long run.

View on HN

SwiftUI provides a completely new UI programming paradigm using the reactive model popularized by web frameworks, RxSwift, etc.

Using UIKit is just Apple current implementation strategy right now. That doesn’t comprise the SwiftUI model & semantics in any meaningful way. It doesn’t feel at all like a wrapper over UIKit IMO. It’s a completely new beast...

It wraps UIKit in some instances. But not most.

I would say that most SwiftUI controls instantiate UIKit views under the hood.

UIKit or WatchKit or AppKit depending on the platform

Reply on news.ycombinator.com