Having used Qt in C++ for a decade or more in the past I just can't see them integrating idiomatically into any language, they don't even manage that in C++ with their giant case of 'not-invented-here' syndrome.
this post was submitted on 10 May 2025
50 points (98.1% liked)
Rust
6908 readers
26 users here now
Welcome to the Rust community! This is a place to discuss about the Rust programming language.
Wormhole
Credits
- The icon is a modified version of the official rust logo (changing the colors to a gradient and black background)
founded 2 years ago
MODERATORS
potentially escaping the notion that because Qt is C++, it is not as safe to use.
How does this even potentially escape the notion? Qt is still C++, and still unsafe, no matter what you use for the rest of your application. And the fact that Widgets is being left out in the cold doesn't sit well with me either.
They still won't even say what these "bridges" are, other than it "does not necessarily replace existing bindings". Does that mean it's still yet another binding?
What would have been really nice IMO are some plain C bindings, for both widgets and QML.
Yeah, any details published so far have been rather vague. I like the prospect of writing my backend UI logic in a memory safe language, but that falls short of benefiting from doing so end to end.
Supposedly Qt would be in a decent position to use their own static analysis and testing frameworks for hardening such bridge interfaces, but using a memory safe system programming language for everything would be ideal. Are there any Rust based UI projects that are looking at ISO certification to ease integration as a Software of Unknown Pedigree?
Rust bindings for Qt would be pretty awesome.