34
Slint 1.14 Released
(slint.dev)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 21 Oct 2025
34 points (97.2% liked)
Rust
7950 readers
2 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
Something to keep in mind is that Slint is not an Open-Source project. If you'll want to improve Slint you'll have to give away your contribution under the MIT No Attribution License (MIT-0) license, yet if and when you'll want to use Slint, you can get it as a paid or GPLv3 license.
In my mind this is more of a ~~proprietary project~~ closed development model (EDIT for correctness, see comment below). The development model is not around freedom and equal rights, with the project being able to stop giving you access under any open-source license whatsoever, all while continuing to use your contributions.
It's not unfair. In fact, it might be a great project. Just not open-source as a project overall, if you care about this.
@vas @u_1f914 Uhm, sorry, but that’s not how it works. They’re making the project available under GPLv3, which is an OSI-approved open-source license. So yes, it is open source.
It has restrictions, including some that you may care about. But that doesn’t mean it’s not open source.
#OpenSource
Fair enough, thanks for the correction. I should be more careful with my wording. I think it's "open-source", but not an "open-source project". In a sense that, they release the source code under a restrictive license, but they themselves will not have it this way and can stop publishing the code any time they want.
So they publish the source code under an OSI-approved license as you say, but they don't develop it in an open manner and I think it's fair to say that they are not an open-source project.
@vas Yeah, that’s fair too. The project behind it is indeed a commercial entity, hence why they set it up that way.
Personally, I wouldn’t be too concerned about them failing to publish new versions, because then the last version will still remain open source forever. And even projects with an open governance model can run out of steam, so the risk might not be any greater here. But yeah, it’s good to be mindful of the risks and restrictions when starting any new project.