Behold, a Linux maintainer openly admitting to attempting to sabotage the entire Rust for Linux project:

https://lwn.net/ml/all/[email protected]/

The good news is this doesn’t affect drm/asahi, our GPU driver. The bad news is it does affect all the other drivers we’re (re)writing in Rust, two so far with a third one coming.

Another choice quote, calling R4L “cancer”: https://lore.kernel.org/lkml/[email protected]/

Personally, I would consider this grounds for removal of Christoph from the Linux project on Code of Conduct violation grounds, but sadly I doubt much will happen other than draining a lot of people’s energy and will to continue the project until Linus says “fuck you” or something.

As for how to move forward, if I were one of the Rust maintainers, I would just merge the patch (which does not touch code formally maintained by the dissenter). Either Linus takes the pull, and whatever Christoph says is irrelevant, or he doesn’t, and R4L dies. Everything else is a waste of everyone’s time and energy.

Edit: Sent in my 2 cents: https://lore.kernel.org/rust-for-linux/[email protected]/T/#m1944b6d485070970e359bbc7baa71b04c86a30af

  • genuineparts@infosec.pub
    link
    fedilink
    arrow-up
    1
    ·
    9 days ago

    You know as someone so far removed from kernel development as I am I have to say that Rust devs are the most annoying fanboys there are and ngl if this kills R4L I won’t even notice aside from those drama threads dissappearing. Just write your own Kernel in Rust if you must. With Blackjack and Hookers.

  • FizzyOrange@programming.dev
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    9 days ago

    His point could be valid, if C was working fine and Rust didn’t fix it. But C isn’t working fine and Rust is the first actual solution we’ve ever had.

    He’s just an old man saying we can’t have cars on the road because they’ll scare the horses.

  • onlinepersona@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    arrow-down
    1
    ·
    10 days ago

    Good grief. People like this Chris dude hold progress back. I’ll keep banging the drum (to be heard by not a single kernel dev, but anyway): the linux kernel need 90% of the Linux Foundation’s funding, not a mere 2%. There should be so many people wanting to be a maintainer that people who openly declare that they want to get in the way like this are easier to remove.

    Anti Commercial-AI license

  • kbal@fedia.io
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    9 days ago

    In this thread, much the same as in any discussion of the topic, we learn that Rust is vital to the survival of the Linux kernel and we’re surely doomed without it, and that the absence of languages other than C in the Linux kernel is the only thing preventing the demons of chaos from arising to tear our souls to shreds and we must remain pure.

    • MadhuGururajan@programming.dev
      link
      fedilink
      English
      arrow-up
      0
      arrow-down
      1
      ·
      9 days ago

      looks like a lot of people want to die on the C programming hill. Cannot blame them, they have no will or ability to keep learning in an industry that *checks notes* …asks you to keep learning!

  • MrPoopyButthole@lemmy.dbzer0.com
    link
    fedilink
    arrow-up
    0
    arrow-down
    1
    ·
    9 days ago

    As a programmer who integrates many languages together in the same product this is a pretty clear line in the sand. Where the languages interface, it’s up to the new language to adopt the interfaces offered by the older language. Rust guys said they will do this, C guys said why don’t you assume this responsibility (they already are). This is either a miscommunication or deliberate scape goat reasoning and deflection. There is no good reason why two languages can’t work together with interfaces. I think the C guys are old, grumpy and fearful.

    Disclaimer: I don’t even like Rust as a language. Just calling it how I see it.