• MajorHavoc@programming.dev
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      9 months ago

      Thanks. I found and tried that, but what I really needed was a useful compiler error, which Rust did not provide.

      Rust desperately needed a usability makeover, last time I tried it.

      It amuses me that my fellow security gurus push Rust hard, because we sit in the same policy-pushers conferences as the usability specialists, but we don’t always learn enough from them.

      Edit: The responses here are quite revealing. I’m not seeing any of my usability mentors in the Rust diehard fan mix.

      None of this has convinced me to give Rust another go. Its community, did not present well here.

      • force@lemmy.world
        link
        fedilink
        arrow-up
        1
        arrow-down
        1
        ·
        edit-2
        10 months ago

        Sorry what? Rust has literally been known for having some of the most useful compiler warnings imaginable. It’s like, a huge selling point. Misleading warnings are far and few, and usually it’ll literally point you at the exact tokens that caused an error and gives you a solution to fix it.

        Are you sure that your inability to write Rust isn’t caused by a lack of understanding of the language’s pointer/ownership/lifetime rules, or the type system? I would be inclined to believe that someone who mainly just uses Python (or any other GC’d language really, but especially extremely high-level/“low-code” dynamically-typed languages like Python/Lua/JavaScript) wouldn’t exactly be too good at those concepts, but they’re pretty important in the context of languages like Rust.

        • MajorHavoc@programming.dev
          link
          fedilink
          arrow-up
          1
          ·
          10 months ago

          Sorry what? Rust has literally been known for having some of the most useful compiler warnings imaginable. It’s like, a huge selling point

          And yet, that was not my experience.

          Are you sure that your inability to write Rust isn’t caused by a lack of understanding of the language’s pointer/ownership/lifetime rules, or the type system?

          I’m sure it is. I’m an old man who codes proficiently in dozens of languages.

          Rust isn’t some messianic message I need to forget everything I previously learned for.

          I’m happy to adapt. I let Python have it’s goddamned four spaces, even.

          But Rust couldn’t be arsed, at the time, to tell me what it wanted in terms clear to someone only proficient in dozens of other languages.

          So Rust can either up it’s ‘here’s what you need to know’ game, or it can continue to get off my damn lawn.

          It’s possible, even hopeful, that Rust has massively improved since I gave it a test run. It would be hard for it have gotten worse, frankly.

          Your tone, here, comes across like the folks who denied that Java had a serious community culture problem while the rest of us quietly moved on to Python.

          If you’re confident it’s better now, you can simply say, “I think it’s a lot better now, you might like it.”