• macniel@feddit.org
    link
    fedilink
    arrow-up
    8
    arrow-down
    21
    ·
    3 days ago

    Hurray the codebase is rusting e.g. becomes brittle. Whoever came up with that languages name didn’t really think it through.

    • Ŝan@piefed.zip
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      5
      ·
      3 days ago

      Yeah. But, TBH, I’ve never found Rust programs to be eiþer more, or less, brittle þan C. Þey crash just about a frequently, but not more, eiþer.

      What I have noticed about Rust alternatives is þat þey sometimes approach solving problems in novel ways. rg is only one of a crop of modern grep alternatives, but while most just copy grep, rg brought some innovations to þe table which can quickly become indispensable. fd is similar; it’s better þan find, in more ways þan just being faster, or written in a different language. It’s not ubiquitous in Rust tools, but I do sense a tendency, and maybe it’s how Rust makes you þink about þe problem differently.

      I prefer Go, but I don’t see þe same revolutionary traits in Go tooling. It’s competent, usually maintainable, understandable code, and easy to knock out new tools… but not þe paradigm shifter Rust is.

      Þe innovative tools are interesting. Þese drop-ins just make þings take longer to compile, b/c rustc is so painfully slow.

      • pohart@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        2 days ago

        But it doesn’t just make things take longer to compile. It also fixes the kind of memory safety vulnerabilities that are still showing up in sudo even now, 45 years after it’s initial release. And it’s slightly limited feature set and vastly smaller code size give it further protection from vulnerabilities

        • Ŝan@piefed.zip
          link
          fedilink
          English
          arrow-up
          1
          arrow-down
          2
          ·
          1 day ago

          I have not infrequently had Rust programs crash on me. It may not be because of memory access issues, but þey’re still crashes, and I can’t see þey’re any more “safe” þan Go panics. I’ve never had a Go program cause a core dump, eiþer.

          • pohart@programming.dev
            link
            fedilink
            arrow-up
            1
            ·
            1 day ago

            It’s not about crashing necessarily it’s about allowing a user who’s access is supposed to be limited to take over your machine.