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.

  • refalo
    1·
    50 minutes ago

    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.

  • taladar@sh.itjust.works
    8·
    10 hours ago

    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.