[pejrich]

I'm just finshing up my first macOS app. I went with SwiftUI because I was new and didn't want to learn an "old" tech. The reality is outside of very basic stuff, SwiftUI is not capable of doing a lot of stuff, so I ended up have to learn not only AppKit as well, but how to fuse AppKit into SwiftUI and fuse SwiftUI into AppKit.

My advice is don't be attracted by the shiny toy that is SwiftUI. It's a steaming pile to dung, unless you just want some basic forms/tables/text.

[nocsi]

It’s probably more productive to mention what about SwiftUI is a “steaming pile of dung”. For most mobile UI, you can spit out a working design faster than w/ AppKit. It doesn’t even have to be one or the other, you can meld both.

What’s the value in talking about SwiftUI being incapable when you don’t mention what you can’t do in it.

[saagarjha]

It doesn’t support a lot of what you can do in AppKit at the moment. There are also many bugs in it where it will throw asserts or stop working or draw incorrectly.