Pricing can change. Yes, there's a perpetual "Buyout" license for $5k, but they can probably just rename the product and claim it's a new one (or add a second product and add commercially relevant eggs to that basket; Qt has tried with things like "Qt for Device Creation" and "Qt for Automotive").
The open source option is not backed by a poison-pill protection like the Free Qt Foundation agreement either.
I know the people behind Slint, and I have a lot of trust toward them. But ownership can change, too.
"We believe that open-source software development and communities are the foundation for a healthy ecosystem of high-quality software, where everyone can learn, improve and give back. We commit to upholding this foundation and pledge by promising to continue to develop Slint in the open under an open-source license compliant with the Open Source Definition.
Further, we commit to provide a royalty-free license for those who develop desktop or web applications and do not want to use open-source components under copyleft licenses."
The royalty free is even better than the LGPL for Rust because rust doesn't support dynamic linking or even re-linking with object files.
Lots of GUI native, non-web libraries have been started in Rust, but they are VERY far from being close to what Qt supports. You may get closer using web based libraries (Tauri, etc), but I wouldn’t personally start web based desktop applications.
Which on that note, last I knew getting Qt apps correctly stripped and packaged for all platforms was a bit of a bear. In particular I remember building Mac application bundles being messy.
That said, I really think Qt should have a separate commercial license that is exactly like LGPL but allows you to link statically and costs much less (without all the enterprisy things).
Yes, things have changed. So annoying you can't just download an offline installer using a mirror of your choice, for example.
> One problem with Qt is that some modules are under the GPL and it is easy to end up inadvertently with a GPL dependency.
I never encountered such a problem, the GPL modules always seemed very niche and targeted toward specific industries (automobile, etc).
1. Nothing in copyleft licenses forbids you from making a living or receiving money.
2. Since the post was about writing an effect for KWin and your alternatives do nothing of sort… perhaps they aren't really valid alternatives, at least in this context.
Source: I work in a company that heavily uses Qt
Qt is LGPLv3 + GPLv3 which are clearly open source licenses.
My understanding is that it's $3,950 per year just to develop using their libraries on your own computer if you ever in the future intend to commercialize your project using QT. Transitioning from the open source license to the commercial license is something you can do but it's not the happy path according to their FAQ.
https://www.qt.io/pricing
My understanding is that some of the QT libraries or older forked versions of them are still completely under open source licenses but it seems like a very complicated situation if you have commercial aspirations with your project.
Something like Slint (Rust based but includes CPP and JS bindings) is not as comprehensive (yet) but it's more modern and the licensing terms are significantly more in line with software industry norms.
GPUI from Zed is also something to monitor: https://www.gpui.rs/
Also, in general you can find an extensive list of Rust-based native UI libraries here: https://areweguiyet.com/