• SuperFola@programming.dev
    link
    fedilink
    English
    arrow-up
    27
    arrow-down
    4
    ·
    4 months ago

    I’m getting fed up about all those articles “rust x something: the future?”, “I rewrote <cli tool> in rust it’s now memory safe”. I get the rust safeties and all, but that doesn’t automatically make everything great, right ? You can still write shit code in any language that can RM -rf all your disk, or let security gaps here and there without intending to.

    • sweaty@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      4 months ago

      Yes security issues will remain a problem no matter what language was used. You are talking about the possibility of a logic flaw being there, whereas rust ‘just’ prevents memory corruption.

      Which is the more common security issue? Memory corruption by a mile. That’s why many are excited by the rust rewrite

      So you’re right it isn’t literally everything, but I’m not sure what would be. What would make you not fed up about it?

    • Asudox@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      4 months ago

      It does make stuff great. Even Microsoft is trying out Rust in their shit operating system because apparently 30% of all CVEs are related to, you guessed it, memory issues. And Rust will most likely solve them all. Even the Linux kernel has Rust code in it now. If Rust was not of importance, why would the Linux kernel get rusty? Especially Linus Torvalds is very strict about these things. Sure, bad code rewritten in Rust does not make it any better than it originally was. Plus you get C-like speed with good syntax and memory safety, what more could you ask for?