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.

  • onlinepersona@programming.dev
    link
    fedilink
    arrow-up
    1
    ·
    13 days ago

    In this thread: people who believe the myth of the safe C programmer. The one who has memorized the spec and is able to hold endless context in their brain while writing code. They themselves are C compilers.

    • eleijeep@piefed.social
      link
      fedilink
      English
      arrow-up
      1
      ·
      13 days 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
        1
        ·
        12 days 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

      • ISO@lemmy.zip
        link
        fedilink
        arrow-up
        0
        ·
        13 days 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
          0
          ·
          13 days 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
            1
            ·
            edit-2
            13 days ago

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

  • ZILtoid1991@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    13 days ago

    If only there were a few alternatives to Rust for system development with a syntax that isn’t a marriage of flesh between OCaml and C. Unfortunately none exists, because if I say otherwise, rustacerans will accuse me of “FUDposting”, and some will even try to dig up some dirt about me, to ruin my life and to ultimately force me off the web, because shame is good, except if they’re the target of said shame.

    So we’re left with a language that:

    • Was marketed as a functional programming language until people started to “FUDpost” about how functional programming has its own issues (optimization, etc.), so the Rust team quickly tried to course correct and market it as a “multi paradigm” language. It is “FUD” if you ask why it’s still const by default. If only Oracle found out about this tactic, to market Java as a “multi paradigm programming language”, because you can just “opt out from OOP aspects”, then tell its usiers that “packaging classes are just good practice”.
    • Makes many optimizations very ugly if not impossible.
    • Makes memory unsafe operations ugly, to “disintensivise the programmer from them”.
    • Has a pretty toxic userbase, which is only being called out by Lunduke-style toxic morons with anti-woke brainrot, and for the wrong reasons. No, the problem isn’t that many people in the Rust community are often trans, and that the code of conduct aren’t a selection of Bible-verses, but that a portion of Rust users weaponize callouts, with this callout weaponization actually coming from 4chan and other sites that pioneered networked harassment.
  • Lucy :3@feddit.org
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    14 days ago

    Understandable. I’d have been admitted to the asylum (again) after just a few hours of ‘working’ with Rust.

    What? Rust syntax is fucking awful. Ugly, unlogical, unreadable. The build process is fucked up as well.