Biden administration calls for developers to embrace memory-safe programing languages and move away from those that cause buffer overflows and other memory access vulnerabilities.

White House urges developers to dump C and C++::Biden administration calls for developers to embrace memory-safe programing languages and move away from those that cause buffer overflows and other memory access vulnerabilities.

  • ben@lemmy.zipEnglish
    275·
    10 months ago

    Probably a good idea, plenty of languages out there that can give good performance while being memory safe nowadays.

    • hagelslager@feddit.nlEnglish
      6·
      10 months ago

      Such as? (Non-programmer here, so I don’t know the ins and outs of programming languages.)

      • ben@lemmy.zipEnglish
        8·
        10 months ago

        Zig and Rust come to mind, at least for replacements for low level languages.

      • lolcatnip@reddthat.comEnglish
        2·
        10 months ago

        Rust is the main one for the kind of code that’s typically written in C++. Most memory-safe languages make big compromises on performance, but Rust code tends to run about as fast as comparable C++ code.

        • scharf_2x40@lemmy.worldEnglish
          71·
          10 months ago

          Isn’t that only microsoft exclusive and closed source? Also does compiling it really yield the same speed as C, it is garbage collected isn’t it?

          • 𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.dbzer0.comEnglish
            8·
            10 months ago

            Was always possible to compile+run C# on Linux using the Mono project. Until Microsoft “bought them out” and created .NET Core, a cross platform version of .NET that MS now encourages people to use instead…

            Microsoft’s new linux compile tools rub me the wrong way slightly, with the telemetry that’s opt-in by default.

            Mono is still extremely valuable for older .NET Framework apps under WINE though, way easier to setup compared to the official installers from what i’ve experienced.

            No idea how compiled C# compares to C…