Given that most of these have bindings to many languages, I don't understand why one would involve a browser-runtime and whole other set of technologies.
Two Qt apps that I use are Calibre and Ripcord, the two ugliest apps on my computer. Not that I'm complaining, but never lines up with HN's why-would-you-use-a-browser Qt praise.
The fact that it's possible to not build an "app that looks native or actually looks good" doesn't imply that it's impossible to build one that does, though.
And I actually tend to prefer wxWidgets, as this wraps the platform's native widgets proper, whereas Qt reimplements many (all?) widgets, but attempts to offer a native look-and-feel.
Regardless: Actual GUI-frameworks have huge advantages to using a browser, like:
- Better performance
- Visual and UX consistency (HCI, people!) on a shared platform
- Smaller sized apps
- Drastically reduced resource and energy usage
[0]: https://en.wikipedia.org/wiki/Category:Software_that_uses_Qt