you are viewing a single comment's thread
view the rest of the comments
[–] 49 points 1 year ago* (last edited 1 year ago) (8 children)

Btw for me persona problem of this replacement is only license switching from strong copy left to permissive, I don't really like this trend it smells really bad from what corps actuality like more nowadays as fear as fire gpl.I don't know who exactly staying behind rust coreutils but devs just ignore all request about GPL or responding very cold or find any other stupid excuse like they don't wanna deal with it. At least they could give their direct point of their views and their motivation about it.but still will not support MIT licence as for main tools for importan core of system

  • source
  • parent
  • hideshow 8 child comments
  • [–] 7 points 1 year ago (2 children)

    Maybe I'm missing something, but I'm not sure what the worst case scenario is... like, is some company going to get rich off of their proprietary cp and sudo implementation that they forked off of an open one?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 1 year ago

    It's one thing when a company gets the benefits of people's contributions and doesn't give back (in the form of source code when they build upon it and at the time they offer binary files). If a company wants to do the work themselves.. well now they don't have too.

    GPL promoters typically value software freedom, and may believe it's generally bad for society when software is proprietary. I don't know what coreutlis does but I doubt there's a thoughtful reason to choose MIT license for a clone.

  • source
  • parent
  • [+] -12 points 1 year ago* (last edited 1 year ago) (3 children)
  • [–] 21 points 1 year ago* (last edited 1 year ago) (2 children)

    I understand the sentiment.

    The move to a permissive license opens the door for these tools to possibly become closed source one day.

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

    You know that you can change license of software that you own copyright to? You can take GPL code and change it to something else, but you can’t un-GPL existing released code. It’s the same thing with MIT.

    The only people bound by the license are people who use it because it is licensed to them.

    The difference is that organisation may develop MIT software without publishing their code.

  • source
  • parent
  • load more comments (-1 replies)
  • load more comments (-1 replies)