Qt

“I have worked in C++ (primarily within the Qt framework which pushed hard into const refs instead of pointers) and it's fine.”

“professional toolkit and properly implemented accessibility features (with a lot of bugs and horrible API because Qt)”

“for my app I run tests across a wide range of laptops, platforms and distros, across nvidia / intel / amd / llvmpipe / ... and it all works fine”

“There's software written today in Qt that traces back all the way to the mid 90s and are still top-of-the-line for their business.”

“They are rather thorough though, making sure their OS-specific theme matches the look and behavior of the native OS”

“Major GUI frameworks such as Qt have hotkey schemas and conventions that are used by default in every program built with them”

“Qt is fully of bugs on Wayland, some of which are unfixable because the API makes guarantees that are impossible to uphold.”

“I can write one using Qt, EGUI, etc (Or many other options), and it will just work on Windows, Mac, Linux/Wayland, and Linux/X.”

“Yes, Qt is mature and high-quality software. If you're doing OSS, then Qt is truly a no brainer.”

“The good thing about Qt: if you don't like the calendar dropdowns, just build your own and customize it.”

“we are already using QT which has a tool for the job, and the QT tool works with the rest of the QT ecosystem”

“even "native" cross-platform applications hardly go through the trouble to target the platform-native UI framework (and instead they go through non-native frameworks like Qt)”

“Frameworks like Qt(widgets) provide reasonably wide range of widgets and you would use them as is.”

“They did a better job of maintaining a coherent visual theme that says "Windows" and fits the design patterns”

“Not all components are LGPL, so when you're doing LGPL and you suddenly need some must-have-but-not-LGPL component,you're in trouble.”

“Qt is the only good choice, even though it's still far from mature after 30 years of development.”

“Which one? The classic QtWidgets, which implements consistent controls but sometimes talked about as deprecated”

“if you're going for a good codebase and simple implementation for a desktop application, QT is way easier”

“None of the UI frameworks is perfect. Neither the ones from Microsoft, nor the ones from Apple, nor Qt”

“A cross platform app which uses something like GTK or QT will be a massively better experience for your users”

“I have no complaints using Qt for cross-platform development, it has been paying my bills for the last 15+ years.”

“I would argue something like Qt is much more viable in $current_year for cross-platform development.”

“Qt5/Qt6 frameworks sooner or later cause more problems than they solve, and require a lot more maintenance/support.”

“it requires paid license if you don't want to abide with (L)GPL license, which should be fair deal, right?”

“GTK-rs and QT are standard - but you'll never have something that looks consistent on every environment.”

“Maintaining three separate UI stacks (WinUI, SwiftUI, GTK/Qt) is dramatically more expensive and slower to iterate on”

“Qt is not a horrible mess to use, the problem is just people don't bother to learn any tech stack outside web.”

“none of the Rust toolkits is half as good as the surviving frameworks, like C++ Builder, Qt, wxWidgets”

“Desktop programs performed better 20 years ago when everything was written in Win32, Qt, GTK and others”

“I think Qt would yield better results than Wine for most things. But since your comment suggests that you're making proprietary software, I think you would have to take special care with linking or else submit to the Qt Group's commercial license terms.”

“It forces one to build the entire app in C++, and that's because, although open-source, its design revolves around the needs of the paying customers of Trolltech”

“Qt apps have to draw a simplistic makeshift titlebar which doesn't match anything when running under GNOME”

“Give me QT to make cross-platform applications that properly manage resources, have low latency, and barely register in memory usage.”

“takes care of all these small but important details that takes time to figure out that Qt isn't equipped with built-in.”

“promote already existing huge toolkits that do have lots of functionalities built-in, including accessibility, like Qt for example”

“it's just that not enough effort was put into making the built-in components behave and look like those on the platforms it runs”

“QT used to be completely inaccessible, although they've significantly improved in the last couple years”

“Either you go LGPL or you have to pay big money for a commercial license, which will then infect all other apps as well.”

“Qt6 can look quite nice with QSS/QStyle themes, these days, and its native affordances are fairly good.”

“The first time I was able to compile a qt app to Linux, windows, Mac, and wasm targets, I was so tickled”