Every week or so there seems to be drama about some old dude shouting about how rust in the Linux kernel is bad. Given all the open hostility, is there easier way for R4L to continue their work?

  • generallynonsensical@lemmy.ca
    link
    fedilink
    English
    arrow-up
    8
    arrow-down
    3
    ·
    2 days ago

    I don’t understand why they haven’t yet. Prove your rust kernel is more efficient than the C/C++ kernel and it’ll be adopted.

    • thingsiplay@beehaw.org
      link
      fedilink
      arrow-up
      11
      arrow-down
      1
      ·
      2 days ago

      There is no point in forking. The problem is not adding Rust to the Kernel, the problem is the C developers to get to work on it together. Forking does not solve this issue. Its not about proving being more efficient or not.

      • 0x0@programming.dev
        link
        fedilink
        arrow-up
        5
        arrow-down
        1
        ·
        1 day ago

        the problem is the C developers to get to work on it together.

        Perhaps the problem is you wanting developers to work on something they don’t want to work on.
        The problem is wanting to shoehorn a new language into an existing, long-standing large-codebase project.
        Forking is the obvious solution but rustaceans know that’s a pretty daunting task…
        The next best thing is to develop in parallel, refactoring parts (usually drivers) without interfering with the existing codebase.

        • thingsiplay@beehaw.org
          link
          fedilink
          arrow-up
          4
          ·
          1 day ago

          Forking does not solve the problem, it only escapes it. Its waste of time and effort in this case. The solution is that the devs work together. Otherwise it makes no sense to have Rust if no one works together. Discussion is the best way to handle this and to come to a solution. Its such an important topic that you have to discuss it, this is healthy, this is how it should be done. This is how its done.

          • 0x0@programming.dev
            link
            fedilink
            arrow-up
            2
            ·
            1 day ago

            If people can’t work together, forking usually “solves” the problem.
            Let’s see if they end up working together.

            • thingsiplay@beehaw.org
              link
              fedilink
              arrow-up
              4
              ·
              1 day ago

              Forking does not solve the problem, it escapes it. The problem in the main Rust Kernel will stay, not working together, arguing, while the fork might work for those who work on the fork. This is not a driver or feature where they can fork, work on it separately. It completely misses the point.

    • kbal@fedia.io
      link
      fedilink
      arrow-up
      15
      ·
      2 days ago

      There is no reason for it. The odds of success would be low compared to the current process which for the most part is going along pretty well despite all the melodrama surrounding it.

      • generallynonsensical@lemmy.ca
        link
        fedilink
        English
        arrow-up
        5
        arrow-down
        1
        ·
        2 days ago

        I agree 100%. I was just commenting that those creating the drama should go waste their resources to reinvent the wheel. See what they can come up with. Gets them and their nonsense out of my feeds for a bit.