Rust lobbyists winning

  • Owl [he/him]@hexbear.net
    link
    fedilink
    English
    arrow-up
    16
    ·
    7 hours ago

    Which do you think happened?

    • Honest appraisal of C++ security problems

    • They figured out some security hole in C++ programs that makes them even worse than we thought

    • Some contractor bribed them to say this so that they can get contracts porting stuff to Rust

    • Some contractor dug up new legitimate security holes in C++ programs so they can convince the FBI to say this so they can get contracts porting stuff to Rust

    • High ranking FBI officials are rust fanboys

    I think contractor bribes, but I think that last two are fun.

    • blobjim [he/him]@hexbear.net
      link
      fedilink
      English
      arrow-up
      10
      ·
      7 hours ago

      It’s just the obvious thing. C and C++ don’t have safeguards against dangerous programming mistakes. Programming languages exist that do. There are to this day still software vulnerabilities being caused by subtly incorrect code that C and C++ require being treated as legitimate.

      • brainw0rms [they/them]@hexbear.net
        link
        fedilink
        English
        arrow-up
        5
        ·
        5 hours ago

        C and C++ don’t have safeguards against dangerous programming mistakes.

        This is not really true for modern C++… and if you’re talking about code bases that use an ancient dialect of C++ where it might be true, the fantasy of even having the option of porting to Rust is actually pretty laughable. C will continue to be necessary for many critical things because there simply isn’t sufficient compiler support coverage for Rust to take the throne.

        • sexual_tomato@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          4 hours ago

          The difference here is that it takes discipline and training to use only those parts of C++. That requires humans in the loop to enforce those decisions. Humans are fallible.

          If you make it impossible at the language level then there’s nothing to train. You just can’t do the thing unintentionally.

          And they didn’t specify Rust; the aerospace industry has been using Ada for decades when it comes to mission critical stuff. Ada’s compiler has long had a similar notoriety to rust’s regarding the difficulty curve.

          • smpl@discuss.tchncs.de
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 hours ago

            My guess would also be that most enterprises prefer Ada over Rust, because Rust lack standardisation. Sometimes you need to do unsafe things though and your billion dollar rocket explode.

  • TheDoctor [they/them]@hexbear.net
    link
    fedilink
    English
    arrow-up
    28
    ·
    9 hours ago

    They’re currently exploring using AI to mass translate software from C to Rust, which will be hilarious if it doesn’t cause Armageddon

    • urmums401k [none/use name]@hexbear.net
      link
      fedilink
      English
      arrow-up
      37
      ·
      8 hours ago

      I’m actually in favor of this. It’s a really good idea, and I hope the state uses it for all the important databases they’re gonna use to put us in the camps.

      Please dont be a hater. Comrade AI might just save lives here.

    • blame [they/them]@hexbear.net
      link
      fedilink
      English
      arrow-up
      11
      ·
      8 hours ago

      that seems like it wouldn’t work very well except maybe for small programs. the kinds of bugs they’re trying to catch and prevent here may need substantial changes to the program’s design in order to prevent. Like the borrow checker literally does not exist in C and it is not a thing people thought about when writing asynchronous C code. Maybe the AI will take a shortcut and write a bunch of unsafe rust code, but in that case what’s the point?

    • bobs_guns@lemmygrad.ml
      link
      fedilink
      English
      arrow-up
      4
      ·
      7 hours ago

      This won’t work completely. Large language models usually fail thoroughly when writing Rust code as there’s not as much training data.

      • kittin [he/him]@hexbear.net
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        11 minutes ago

        My only real criticisms of rust are aesthetical. I never liked how C++ is full of macros and :: and <> and rust inherits that a bit.

        I use Go because of the work I do right now, which is deep in Kubernetes and APIs for which Go is just more convenient. Protobuf and K8S are of course supported by rust and many other languages as well, but in Go it’s simply easy… Go was designed from the bottom up to write APIs basically so it’s good at that. And most, almost all, of the K8S ecosystem uses Go which means I’d need a good reason not to use Go for that since standardization, interoperability, and ecosystem are key concerns.

        You can use rust for this too, for sure no problem. But with Go you’re doing all of that pretty much out of the box.

        The Go ecosystem in general is a little bit stronger due to higher adoption, although I wouldn’t really call that a weakness of rust.

        And finally less people use Rust which is another consideration for long term maintenance concerns, but to be fair Go adoption is also low.

        I’m never an evangelist for any language. Well, if I could simply write everything in typescript I would to be honest because I think it’s just swell but obviously its not for this use case, and the above are the reasons why I use Go and get my teams to use Go for the use case of services, Kubernetes controllers, and since we want to use Go for those things we then also use Go for other random things like CLIs etc just because it makes sense to limit tech stack sprawl.

    • also, separate comment, what are you generally building? if you’re writing Go because it’s network code, you might want to look into Elixir. It’s GC but the behavior of BEAM is more soft-RT friendly due to its history in telephony, you might be more at home there

  • OprahsedCreature@lemmy.ml
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    1
    ·
    9 hours ago

    Am I wrong or is this a strong point in favor of c/c++? I’d generally want to do whatever the opposite is of what the FBI would like me to do.

    • GaveUp [she/her]@hexbear.netOP
      link
      fedilink
      English
      arrow-up
      34
      ·
      edit-2
      9 hours ago

      “critical software” here refers to weapons systems, spying systems, government surveillance systems, cyberwarfare software, etc.

      Do you work on critical software

    • blame [they/them]@hexbear.net
      link
      fedilink
      English
      arrow-up
      20
      ·
      9 hours ago

      their reasoning is that rust (and perhaps others) that can be used in place of c or c++ have stronger compile time memory and thread safety checking which are two major sources of bugs and exploit vectors. So it’s not like they’re infiltrating the language in this case the way they would with crypto.

    • bobs_guns@lemmygrad.ml
      link
      fedilink
      English
      arrow-up
      8
      ·
      7 hours ago

      It’s not really a strong point. C++ has its place for graphics programming and gamedev and C has its place for embedded, but Rust would be a better choice for something like a cryptography app to help revolutionaries communicate for example.

    • urmums401k [none/use name]@hexbear.net
      link
      fedilink
      English
      arrow-up
      13
      ·
      edit-2
      8 hours ago

      Right but AI translating of all government code is good. This is what you want, especially if shit goes down. Dont tell your enemy to stop pouring the kool aid.