48
is there something about rust which precludes copyleft licensing? (programming.dev)
submitted 1 year ago* (last edited 1 year ago) by to c/opensource@lemmy.ml
38 comments fedilink hide all child comments
 

I often see Rust mentioned at the same time as MIT-type licenses.

Is it just a cultural thing that people who write Rust dislike Libre copyleft licenses? Or is it baked in to the language somehow?

Edit: It has been pointed out that I meant to say "copyleft", not "libre", so edited the title and body likewise.

you are viewing a single comment's thread
view the rest of the comments
[–] 4 points 1 year ago (1 child)

I don't think it's Rust exactly. I think Rust is just newer and this attracts developers with less experience with licensing. It's not really something developers want to think about very much so they often just use the default. Heck, most code on github, etc., didn't have any licenses at all for a really long time until businesses realized they couldn't use the code without them due to copyright laws being applied by default but patents not being default in many countries, etc.

There are consequences to using copyleft as opposed to more permissive libre licenses, and vice versa, that may not be well understood by a lot of developers in general until they get into a situation where it matters. Either their code can't be used by people they wanted to sue it, or companies are abusing the code without proper attribution, etc.

  • permalink
  • fedilink
  • source
  • hideshow 2 child comments
    •
  • [–] [S] 3 points 1 year ago (2 children)

    It’s not really something developers want to think about very much so they often just use the default.

    Do you think it was intentional ideological decision by the Rust developers or some other contributors/interests to make permissive the default? Or a random decision that has ended up being consequential because of the popularity of Rust?

    I have noticed for a long time that github promotes MIT license. It lets you use any, of course, but puts a real positive shine on MIT. My perception is that this is a purposeful intervention by MS into FLOSS to promote MIT.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 3 points 1 year ago (1 child)

    I think its just that the language having built in licensing is a newer concept as opposed to just having a companion document. And MIT and Apache are the licenses the pieces of the language is licensed under, so they made those default. That way it's a conscious decision to make it more restrictive.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] [S] 1 point 1 year ago (1 child)

    built in licensing

    how's it built in?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 1 year ago

    Rust crates manifest file requires a license be set to be hosted on crates.io and the example manifest file uses:

    [package] 
license = "MIT OR Apache-2.0"

    Something like the Java's jar manifest doesn't have a predefined license property for interpreters to parse. Maven has a property, but it's not required.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 1 year ago

    MS and other corps love MIT and related licenses because they can just take the code and basically do whatever with it in their projects, so it makes sense for them to promote it. Generally speaking, they won't touch GPL/AGPL as it would force them to distribute their source.

    I believe it was a very intentional choice to use a permissive license for Rust. If they hadn't, it would not have been as popular as it is today, nor would it have big money behind it. https://rustfoundation.org/members

  • permalink
  • fedilink
  • source
  • parent