Libraries like PyQt (which Calibre uses, for instance) make it feasible at all. They still won't save you the moment you encounter any platform-specific corner case, of which there are uncountable multitudes.
Tip your OSS projects. They earned it more than you know.
Writing Qt in C++ or using QtQuick is really not that bad
The web is rich with 3rd party support for a lot of things, so as a platform it's attractive. If you need to grow, you can be more confident it will have what you need. But with that also comes a lot of bloat, legacy and poor decisions too.
What frameworks like Qt often suffer from is an outdated or overly restrictive design language which is harder than worthwhile to customize, so you get apps that feel antiquated. Some people aren't as bothered by this as others, and generally I agree it shouldn't matter, but it does.
I strongly doubt so. Eye candy becomes quickly old when you're using the software for hours a day.
Consistency helps more than aesthetics at this point. Shared metaphors and all that.
On Mac OS, I can almost immediately tell when something is a QT app. It can be a beautifully well designed app, and my hindbrain is just screaming that it's not right. Take QGIS. Looks good, works well. But doesn't feel like a Mac app.
And it's not even about following all the Mac conventions. Sure, I like the Mac style preference panes OmniGraffle and Transmit have. But the telegram Mac client, written in swift, has it's own weird preference system, and still feels "right"
Electron apps, ironically, don't trigger the uncanny valley effect. Maybe it's because they all bring their own UX, instead of trying to ape platform ux, maybe it's because the font and other rendering is more polished, by virtue of being browser descended, but either way, they don't make me feel like I'm interacting with some weird not-quite Mac program.