Read on Twitter
Let's debunk some myths about #SwiftUI 
”It’s buggy and consumes tons of resources”. 99% of the time this boils down to programmer error when it comes to state observation. Using SwiftUI efficiently is all about mastering State, ObservedObject, Environment and Combine. With that sorted, performance is actually amazing.
”It lacks functionality from UI/AppKit”. It doesn’t. It builds upon it. You’re one ViewRepresentable away from *Kit-land. Apple won’t and doesn’t need to rebuild it all in SwiftUI. Pull in whatever legacy view you need and carry on. This is a feature, not a compromise. Use it.
”It obscures the native platform components and doesn’t offer the same customisation”. While the latter is true (for now), Introspection solves all of this. One ViewRepresentable will break the barrier to the *Kit view hierarchy and all its functionality. https://github.com/siteline/SwiftUI-Introspect
”It’s never going to replace *Kit”. It's a question of relevancy, not existance. Remember Carbon? We are in a transition period where *Kit is fading away into a compatibility layer. I’m building next-gen apps in 99% SwiftUI and 1% AppKit code, so I’d argue we’re already there.
