Linux people doing Linux things, it seems.

  • Petter1@lemm.ee
    link
    fedilink
    arrow-up
    14
    arrow-down
    1
    ·
    edit-2
    4 months ago

    They don’t get, that without memory issue resistant language, not a lot of new blood will be as good as them dealing with that stuff since they already have that solved in the language itself.

    It is about making kernel development future proof, so that new devs keep on coming and don’t create massive security holes on the way.

    Well this is how I understand it.

    • leisesprecher@feddit.org
      link
      fedilink
      arrow-up
      27
      arrow-down
      1
      ·
      4 months ago

      And it’s a bad argument anyway. You’re only good at memory management until the first bug takes down production.

      Rust isn’t a panacea and certainly has problems, but eliminating an entire class of potentially very dangerous bugs is a very good argument.

    • Giooschi@lemmy.world
      link
      fedilink
      English
      arrow-up
      15
      ·
      4 months ago

      Note that Rust does not “solve” memory management for you, it just checks whether yours is memory safe. Initially you might rely on the borrow checker for those checks, but as you become more and more used to Rust you’ll start to anticipate it and write code that already safisfies it. So ultimately you’ll still learn how to safely deal with memory management, just in a different way.

      • verdigris
        link
        fedilink
        arrow-up
        7
        ·
        edit-2
        4 months ago

        Yeah all of the times I see Rust being described as “harder to learn” than C I just shake my head. It’s like saying that it’s easier to just fall off the cliff at the Grand Canyon instead of taking the path down. Any additional difficulty is because the language forces you to understand memory and pointers properly, instead of just letting you fuck around and find out.