this post was submitted on 30 Jan 2026
53 points (93.4% liked)
Linux
11550 readers
540 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I appreciate that it's not trying to replace
cpbut the lack of copyleft is always disconcerting.What's the risk here though, a company like Amazon makes a closed source version of it?
If it was a file format library, or something like a web server I'd get it. But stuff like
cpare effectively just userspace wrappers around kernel APIs.yeah, like, supposedly it can be hard to use GPL with some rust dependencies, but the MPL is right there as a decent compromise.
I like and use rust, and I actively try to use permissive licenses for libraries and copy left for binaries. Just makes sense in my head.
I always find choosing a license confusing.
If you're up for it, I would love to read why you use this guideline.
how can it be hard? permissive licenses are compatible to the GPL, the opposite not though
Static linking makes things difficult. I'm not sure what the details are, that's just what I've heard from Rust developers.
Because of static linking, a single GPL dependency turns the entire resulting binary into a GPL licensed one, so yeah just use something like the MPL in that case (Or EUPL, which I hear is similar)
LGPL has the same issue, since it only provides an exception for dynamic linking. But honestly that's all an issue for lawyers and judges to sort out (I bet you could win in court with an argument that dynamically linking to GPL is actually fine).