23
Why are all the rust projects MIT licensed? (monero.town)
submitted 9 months ago* (last edited 9 months ago) by jack@monero.town to c/rust@lemmy.ml
36 comments fedilink hide all child comments

UPDATE: I found this issue explaining the relicensing of rust game engine Bevy to MIT + Apache 2.0 dual. Tldr: A lot of rust projects are MIT/Apache 2.0 so using those licenses is good for interoperability and upstreaming. MIT is known and trusted and had great success in projects like Godot.

ORIGINAL POST:

RedoxOS, uutils, zoxide, eza, ripgrep, fd, iced, orbtk,...

It really stands out considering that in FOSS software the GPL or at least the LGPL for toolkits is the most popular license

Most of the programs I listed are replacements for stuff we have in the Linux ecosystem, which are all licensed under the (L)GPL:

uutils, zoxide, eza, ripgrep, fd -> GNU coreutils (GPL)

iced, orbtk -> GTK, QT (LGPL)

RedoxOS -> Linux kernel, most desktop environments like GNOME, KDE etc. all licensed GPL as much as possible

you are viewing a single comment's thread
view the rest of the comments
[-] rah@feddit.uk 6 points 9 months ago

for tools

For GNU/Linux tools?

[-] snowe@programming.dev 0 points 9 months ago

ok, that I can understand, if they're only considering "tools" to be those on lgpl systems themselves.

[-] rah@feddit.uk 2 points 9 months ago* (last edited 9 months ago)

Firstly, GNU/Linux systems aren't just "lgpl" systems. Secondly, out of curiosity what were you considering "tools" to be?

[-] snowe@programming.dev 2 points 9 months ago

Anything you use on your computer to help you complete a job. Docker, ripgrep, IntelliJ, graalvm, javac, cargo, Zulip, etc. Thinking that tools are just contained to be what comes bundled with your os is a weird take to me.

this post was submitted on 30 Nov 2023
23 points (96.0% liked)

Rust Programming

7734 readers
1 users here now

founded 5 years ago
MODERATORS
nutomic@lemmy.ml
Joe@lemmy.ml
AgreeableLandscape@lemmy.ml