Why are all the rust projects MIT licensed? - eviltoast

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

  • belated_frog_pants@beehaw.org
    link
    fedilink
    arrow-up
    6
    ·
    1 year ago

    A “cuck” license? I have 0 interest in engaging in any meaningful conversation around “we live in a society and rigidity of value measurement cannot be without context” because thats childish at best and a dog whistle of the anti-intellectual at worst.

    • Something Burger 🍔@jlai.lu
      link
      fedilink
      arrow-up
      7
      arrow-down
      1
      ·
      1 year ago

      I’m using cuck in the literal sense, not the MAGA fascist sense. Your code, someone else’s profit. GPL or bust. If corporations want to use the features of a FOSS project without contributing their changes, they can fuck off and rewrite it from scratch.