this post was submitted on 10 May 2025
50 points (98.1% liked)

Rust

6897 readers
62 users here now

Welcome to the Rust community! This is a place to discuss about the Rust programming language.

Wormhole

[email protected]

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
snowe
Ategon
EdTheLegendary
kahnclusions
torcherist
50
Qt Group unveils expansion plans for technology-agnostic Qt ecosystem (www.qt.io)
submitted 2 days ago by ruffsl to c/rust
4 comments fedilink hide all child comments
 

cross-posted from: https://programming.dev/post/30061235

As part of this expansion, Qt Group will introduce new bridging technology that integrates Qt with any programming language of choice, initially including Rust, Python, .NET, Swift, and Kotlin/Java.

I'd really like to use Qt for GUI and HMI development for certified medical devices using embedded hardware, but wasn't looking forward to all the conventional C++ that would have entailed. Looks using Rust with Qt may get better soon?

Second source reporting from Qt World Summit in Munich:

Part of the thinking here is that C++ is regarded as an unsafe language whereas the languages supported by Qt Bridges are safe languages, potentially escaping the notion that because Qt is C++, it is not as safe to use.

you are viewing a single comment's thread
view the rest of the comments
[โ€“] refalo 6 points 1 day ago* (last edited 1 day ago) (1 children)

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.

[โ€“] ruffsl 1 points 1 day ago

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?