> Even on an OSX-only app, I'm sure as hell not using SwiftUI/UIKit/etc. Qt more consistently nails native apps, the so-called-native UI toolkit on any given OS

> Even on an OSX-only app, I'm sure as hell not using SwiftUI/UIKit/etc. Qt more consistently nails native apps, the so-called-native UI toolkit on any given OS doesn't. In my experience this varies a lot between projects and developers. Some Qt apps are great (Krita comes to mind) but just as many are quite janky. Of course AppKit/UIKit have their fair share of bad apps too, but generally if developers have gone as far to commit to building their app with either (especially AppKit, which is the less accessible of the two) they take extra care to produce a good product. Qt being for most intents and purposes usable only with C++ and Python likely impacts this, though. A lot of devs aren't particularly keen on either language, especially with the extra headaches that come with shipping a user-facing multiplatform Python app that reliably runs everywhere.