At first I was sceptical, but after a few thought, I came to the solution that, if uutils can do the same stuff, is/stays actively maintained and more secure/safe (like memory bugs), this is a good change.

What are your thoughts abouth this?

    • ParetoOptimalDev@lemmy.today
      link
      fedilink
      arrow-up
      74
      arrow-down
      2
      ·
      2 days ago

      I would love this news if it didn’t move away from the GPL.

      Mass move to MIT is just empowering enshittification by greedy companies.

      • Zenlix@lemm.eeOP
        link
        fedilink
        arrow-up
        7
        ·
        2 days ago

        What does the license change actually mean? What are the differences?

        • Daniel Quinn@lemmy.ca
          link
          fedilink
          English
          arrow-up
          40
          ·
          edit-2
          1 day ago

          The best example I could point to would be BSD. Unlike Linux, the BSD kernel was BSD (essentially MIT) -licensed. This allowed Apple to take their code and build OSX and a multi-billion dollar company on top of it, giving sweet fuck all back the community they stole from.

          That’s the moral argument: it enables thievery.

          The technical argument is one of practicality. MIT-licensed projects often lead to proprietary projects (see: Apple, Android, Chrome, etc) that use up all the oxygen in an ecosystem and allow one company to dominate where once we had the latitude to use better alternatives.

          • Step 1 is replacing coreutils with uutils.
          • Step 2 is Canonical, Google, or someone else stealing uutils to build a proprietary “fuutils” that boasts better speeds, features, or interoperation with $PROPRIETARY_PRODUCT, or maybe even a new proprietary kernel.
          • Step 3 is where inevitably uutils is abandoned and coreutils hasn’t been updated in 10 years. Welcome to 1978, we’re back to using UNIX.

          The GPL is the tool that got us here, and it makes these exploitative techbros furious that they can’t just steal our shit for their personal profit. We gain nothing by helping them, but stand to lose a great deal.

            • thedeadwalking4242@lemmy.world
              link
              fedilink
              arrow-up
              38
              ·
              2 days ago

              Competitive improvements the company makes make be kept secret, re packaged, and sold without making contributions to the src code.

              Basically embrace, extend, extinguish

              • prime_number_314159@lemmy.world
                link
                fedilink
                arrow-up
                1
                arrow-down
                9
                ·
                2 days ago

                Ideas can only be patented, not copyrighted. If a company designs something novel enough to qualify for a patent, and so good that people willingly pay for the feature, that’s impressive, and arguably still a good thing. If instead they design a better user experience, or an improvement in performance, the ideas can be used in open source, even when the code cannot be.

            • CarrotsHaveEars@lemmy.ml
              link
              fedilink
              arrow-up
              7
              ·
              edit-2
              1 day ago

              Imagine a contributor of the project. He would have been fixing the bug for free and give the work to the public project. Right before he submits the code change, he sees an ad from a big tech bro: “Hiring. Whoever can fix this bug gets this job and a sweet bonus.” He hesitated and worked for the company instead.

              Now that he is the employee of the company. He can’t submit the same bug fix to the open source project because it is now company property. The company’s product is bug free, and the open source counterpart remains buggy.

                • philluminati@lemmy.ml
                  link
                  fedilink
                  arrow-up
                  3
                  ·
                  edit-2
                  23 hours ago

                  To give you an example, if git was under the MIT license instead of GPL , then Microsoft can silently add incompatible features to GitHub without anyone knowing. The regular git client appears to work for a while. Then they start advertising msgit with some extra GitHub features and shortcuts. Once they get to 50% adoption they simply kill the open source version off.

                  If GitHub required a special client to be installed tomorrow… I would have to concede and use it. It’s GPL that stops that because everyone has to get every new feature.

                  When Slack was first rolling out the dev team in my office of 50 people we all hated it. Thankfully it had an IRC bridge so we could use Slack through IRC. It was seemingly the same experience as before except more business users were in the chat rooms. Once the Corp side of the business were onboard, they dropped IRC support, forcing us to use their clients.

                  Now it doesn’t matter that rules or laws or privacy invasion they do. They have captured the companies communications and can hold it hostage.

                  I’ve seen it again and again. When is the last time you downloaded an MP3 file?

      • priapus@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        4
        ·
        2 days ago

        Genuinely what negative ramifications could come of uutils being MIT licensed? The kernel license isn’t going to change and I really don’t see how companies can abuse uutils for a profit.

    • alphadont@lemmy.ca
      link
      fedilink
      English
      arrow-up
      5
      arrow-down
      3
      ·
      1 day ago

      Okay, I’m not a fan of this either but let’s not get too worried about this. Everyone’s known Ubuntu is a joke for a long time and they don’t really have much influence on even several of their downstreams, let alone the rest of the ecosystem.