[jonhohle]

It’s so bizarre. I wanted to use it for a menu extra and something as simple as animating the icon couldn’t be done. There are several of Apple’s own apps that use animated Menu extra icons and they’re probably doing the same hybrid AppKit/SwiftUI workarounds.

[ChrisMarshallNY]

I won’t use UIViewRepresentable. I feel that it’s a kludge, and kind of negates the whole purpose of SwiftUI. I know that some of the “native” types are probably UIViewRepresentable, under the covers (like maps), but I feel as if it’s a “duct tape” solution. Also, some of the code gymnastics that I need to do, in order to implement “non-standard” functionality, are pretty crazy. SwiftUI makes it absurdly easy to do stuff that follows the intended workflow, but completely falls down, if you stray off the path. UIKit complains, but grudgingly goes along with you.

I actually want SwiftUI to work. I think they have a good idea, but it’s a massive undertaking, and really, breathtakingly ambitious, when you consider what it’s trying to do.

UIKit represents a mature tech that has been refined since 2008, and a lot of that is based on lessons learned, implementing AppKit, which has been around forever (especially if you consider that it came from NeXTSTEP, which probably started in the 1980s). With AutoLayout and UIKit, I can do pretty much anything I want.