Alex Gaynor recently announced he is formally stepping down as one of the maintainers of the Rust for Linux kernel code with the removal patch now queued for merging in Linux 6.19.

Alex Gaynor was one of the original developers to experiment with Rust code for Linux kernel modules. He’s drifted away from Rust Linux kernel development for a while due to lack of time and is now formally stepping down as a listed co-maintainer of the Rust code. After Wedson Almeida Filho stepped down last year as a Rust co-maintainer, this now leaves Rust For Linux project leader Miguel Ojeda as the sole official maintainer of the code while there are several Rust code reviewers.

  • eleijeep@piefed.social
    link
    fedilink
    English
    arrow-up
    2
    ·
    12 hours ago

    the myth of the safe C programmer

    I learnt C around about 1997 and I’ve used it off and on professionally since about 2006. I am not a myth, and there are many others like me.

    What do you want me to write?

    • fruitcantfly@programming.dev
      link
      fedilink
      arrow-up
      6
      ·
      4 hours ago

      What do you want me to write?

      To meet the bar set by onlinepersona, you’d need to write safe C code, not just some of the time, but all of the time. What you appear to be proposing is to provide evidence that you can write safe C code some of the time.

      It’s like if somebody said “everyone gets sick!”, and some other person stepped up and said “I never get sick. As proof, you can take my temperature right now; see, I’m healthy!”. Obviously, the evidence being offered is insufficient to refute the claim being made by the first person

    • Corbin@programming.dev
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 hours ago

      I want you to write kernel code for a few years. But we go to Lemmy with the machismo we have, not the machismo we wish we had. Write a JSON recognizer; it should have the following signature and correctly recognize ECMA 404, returning 0 on success and 1 on failure.

      int recognizeJSON(const char*);
      

      I estimate that this should take you about 120 lines of code. My prior estimated defect rate for C programs is about one per 60 lines. So, to get under par, your code should have fewer than two bugs.

    • ISO@lemmy.zip
      link
      fedilink
      arrow-up
      7
      ·
      11 hours ago

      Can you point to relevant non-trivial public work of yours that has zero CVE’s?

      The more you learn and know, the more you refrain from making such statements. This is universally applicable, and not limited to C or programming. And that’s what makes your “story” suspect.

      Or maybe it’s a reading comprehension issue.


      I used to write non-trivial C code myself btw.

      • eleijeep@piefed.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        11 hours ago

        That’s quite an insulting insinuation, and no, I’m not going to doxx myself on my pseudonymous piefed account.

        What do you want me to write?

        • ISO@lemmy.zip
          link
          fedilink
          arrow-up
          9
          ·
          edit-2
          11 hours ago

          Super-human claims require evidence. And asking for that evidence is not an insult.