karolherbst 🐧 🦀 (@karolherbst@chaos.social)
chaos.social
I'm formally stepping down as a nouveau kernel maintainer. I want to stress out this is only for the kernel side of things and has and will not have any impact on my involvement in mesa. Don't really want to add too much here, just that things need to change. Recent events (tm) is just another example of the deep disagreement. I won't be able to convince people I made up my mind on my own here, so I won't bother with it anyway. Full upstream and public statement here: https://lists.freedesktop.org/archives/nouveau/2025-February/046677.html

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

  • KrispeeIguana@lemmy.ml
    62·
    5 days ago

    From what I remember, it’s much more difficult to accidentally leak memory in Rust. Combined with the drop-in compatibility with C and the somewhat more intuitive (imo) syntax, I can see its popularity as unsurprising.

    I think the biggest thing is that there aren’t really that many reasons not to use Rust.

    • esa@discuss.tchncs.de
      8·
      5 days ago

      Leaking isn’t really the issue, though I suppose Rust helps with that as well. Its memory sales pitch is more about memory safety, which is not reading or writing the wrong parts of memory. Doing that can have all sorts of effects, where the best you can hope for is a crash, but it often results in arbitrary execution vulnerabilities. Memory _un_safety is pretty rare and most prominent in languages like C, C++ and Zig.

      Rust also has more information contained in it, which means resulting programs can actually be faster than C, as the optimizer in the compiler is better informed.