As I mentioned in another comment, I value my GUIs feeling native on my KDE desktop (and not having to reinvent things like QSettings and, last time I tried with GTK+ 2.x, drag-and-drop multi-select for list views) strongly enough that I start with PyQt and then add rust-cpython and Rust if enough of the application can be cleanly encapsulated away from the GUI code to justify the added build-time complexity.
Comments
That depends on your requirements.
As I mentioned in another comment, I value my GUIs feeling native on my KDE desktop (and not having to reinvent things like QSettings and, last time I tried with GTK+ 2.x, drag-and-drop multi-select for list views) strongly enough that I start with PyQt and then add rust-cpython and Rust if enough of the application can be cleanly encapsulated away from the GUI code to justify the added build-time complexity.
Sounds like a nice model. What are the worst disadvantages?
Mainly that, for any portions written in Python, I can't rely on Rust's type system to help me catch mistakes at compile time.
...though Qt's QTest module does help to balance things out a bit, by providing a Selenium-like facility for automating GUI interactions.