• secret300@lemmy.sdf.org
    link
    fedilink
    arrow-up
    1
    ·
    6 days ago

    What exactly makes rust memory safe? That’s the big selling point of it right? Is the compiler just more strict?

  • kbal@fedia.io
    link
    fedilink
    arrow-up
    3
    ·
    2 months ago

    I took notes for the benefit of anyone who doesn’t like their info in video form. My attempt to summarize what Linus says:

    He enjoys the arguments, it’s nice that Rust has livened up the discussion. It shows that people care.

    It’s more contentious than it should be sometimes with religious overtones reminiscent of vi versus emacs. Some like it, some don’t, and that’s okay.

    Too early to see if Rust in the kernel ultimately fails or succeeds, that will take time, but he’s optimistic about it.

    The kernel is not normal C. They use tools that enforce rules that are not part of the language, including memory safety infrastructure. This has been incrementally added over a long time, which is what allowed people to do it without the kind of outcry that the Rust efforts produce by trying to change things more quickly.

    There aren’t many languages that can deal with system issues, so unless you want to use assembler it’s going to be C, C-like, or Rust. So probably there will be some systems other than Linux that do use Rust.

    If you make your own he’s looking forward to seeing it.

    • alyxbond@kbin.earth
      link
      fedilink
      arrow-up
      1
      ·
      7 days ago

      Linus Torvalds has made some interesting comments on the Rust vs C debate in the Linux kernel. He enjoys the discussions because it shows that people care about the project, even though things can get a little heated like the classic vi vs emacs arguments. The Rust conversation is still in its early days, and while Linus is optimistic about its future in the kernel, it’s too soon to say whether it will ultimately succeed or fail.

      He points out that the Linux kernel isn’t just “normal” C it’s C with additional tools and rules that ensure memory safety and other protections. This incremental approach has allowed for changes without causing the kind of backlash that Rust has faced with its more dramatic changes.

      At the end of the day, the kernel has to deal with system-level issues, and unless you’re working in assembly, it’s going to be C, C-like, or Rust. Linus is looking forward to seeing how other systems outside of Linux might adopt Rust for their own needs.

      If you’re interested in exploring more of these tech discussions or maybe looking for some related tools, you can download APK for access to various Linux utilities on mobile.

    • gomp@lemmy.ml
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      I took notes for the benefit of anyone who doesn’t like their info in video form.

      I love you.

      • gerdesj@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 months ago

        Start the linuxa or alinux project and off you trot. Find a better name than I did here and you’ll be fine.

  • thingsiplay@beehaw.org
    link
    fedilink
    arrow-up
    1
    ·
    2 months ago

    You can’t improve and break silence without discussing and making changes. The existing maintainers won’t live forever, having Rust in the Kernel is a bet on the future. Linus wouldn’t have adopted and accepted Rust, if he wasn’t thinking its worth it. And looks like it was already worth it.

  • GravitySpoiled@lemmy.ml
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 months ago

    I don’t want to watch a video about it.

    I’d like to know it, but a couple of sentences wouldn’t have hurt

    • blackbrook@mander.xyz
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      FWIW, it’s a 9 min video and doesn’t contain anything earth shattering or easily summarized. Basically there is some friction between C and Rust devs, and Linus doesn’t think that it’s such a bad thing (there has be interesting discussion) and it’s way too early to call Rust in the kernel a failure.