Following the R4L debacle “you are cancer, you are the problem, we are the thin blue line”, another maintainer steps down from the Linux Kernel

  • catloaf@lemm.eeEnglish
    0·
    22 days ago

    Yup. But based on Linus’ response to marcan’s concerns, it sounds like Linus just wants to ignore the problems.

    • jevans ⁂@lemmy.mlEnglish
      0·
      22 days ago

      Yeah, this looks like trying to avoid conflict by shutting down a person pushing back against bad behavior, instead of trying to mediate the situation to come to a just resolution. It’s shallow and gross and not sustainable.

      • merthyr1831@lemmy.mlEnglish
        1·
        19 days ago

        I think it’s a big flaw of the mailing list system of the kernel development. Marcan’s reaction led to everyone trying to “protect the thread” from being “derailed” and ignore the actual comments that in themselves should’ve been discussed properly.

        Even leads to people here saying Marcan overreacted when I think on other social media platforms this would’ve been its own conversation separate to the conduct of other users.

        I say this purely speculatively since I havent ever held a longrunning group convo in a mailing list intentionally.

    • proton_lynx@lemmy.world
      0·
      22 days ago

      I think that Linus’ concerns about posting on social media is completely valid, but I was pretty disappointed that he didn’t address Hellwig going full retard. Marcan dealt with this like a spoiled child in the end, but he was 100% right.

      If you want to make Linux impossible to maintain due to a cross-language codebase, do that in your driver so that you have to do it instead of spreading this cancer to core subsystems. (where this cancer explicitly is a cross-language codebase and not Rust itself, just to escape the flameware brigade).

      This should be worth a Linus rant in my honest opinion.

      • ikidd@lemmy.worldEnglish
        0·
        22 days ago

        Hellwig specifically says “where this cancer is a cross-language codebase”. He’s not wrong. I don’t know how you transition languages, but my god, if you want to lose maintainers, make it impossible to maintain because of language incompatibilties. A few people from a downstream project like Asahi or an almost defunct driver like Nouveau would be the least of your worries if you were Linus.

        • WalnutLum@lemmy.ml
          0·
          21 days ago

          A few people from a downstream project like Asahi or an almost defunct driver like Nouveau

          I’m not sure why you think Asahi is a minor player in the linux community when they’re responsible in the entirety for porting Linux to the Arm-based Mac M1+ series, or why you think Nouveau is defunct.

          • ikidd@lemmy.worldEnglish
            1·
            21 days ago

            If a single percent of regular Linux users use either of those on a daily basis, I’ll eat a bug. And desktop Linux isn’t even a significant amount of Linux use in general. So why would the kernel developers give the slightest shit about either of them?

            • WalnutLum@lemmy.ml
              0·
              21 days ago

              Nouveau is important because Nouveau is the default driver in Ubuntu, Fedora, OpenSUSE, Debian, and ever other distro.

              Linux distributions can’t easily distribute the proprietary nvidia drivers or the slightly less proprietary nvidia-open drivers so they depend on nouveau as the default nvidia driver. When you install a distro it usually has to use the nouveau drivers before downloading the proprietary blobs from Nvidia.

              Nouveau is the only reason anyone can use Linux on an Nvidia card long enough to install the other drivers.

              It’s also actively maintained, receiving updates that get upstreamed almost daily.

              I’m not sure what about those things says “defunct”.

              And the rust developments in Asahi for the M1+ series of CPUs don’t just benefit Mac but all the ARM CPUs as well.