Google insists it's easy to add Rust code to your firmware
www.theregister.com
Not so much when trying to convert coding veterans

Google recently rewrote the firmware for protected virtual machines in its Android Virtualization Framework using the Rust programming language and wants you to do the same, assuming you deal with firmware.

In a write-up on Thursday, Android engineers Ivan Lozano and Dominik Maier dig into the technical details of replacing legacy C and C++ code with Rust.

“You’ll see how easy it is to boost security with drop-in Rust replacements, and we’ll even demonstrate how the Rust toolchain can handle specialized bare-metal targets,” said Lozano and Maier.

Easy is not a term commonly heard with regard to a programming language known for its steep learning curve.

Nor is it easy to get C and C++ developers to see the world with Rust-tinted lenses. Just last week, one of the maintainers of the Rust for Linux project - created to work Rust code into the C-based Linux kernel - stepped down, citing resistance from Linux kernel developers.

“Here’s the thing, you’re not going to force all of us to learn Rust,” said a Linux kernel contributor during a lively discussion earlier this year at a conference.

    • Strykker@programming.dev
      64·
      2 months ago

      Sure for newcomers to a project like the Linux kernel they have to learn C , because that is what the project is currently written in, but trying to transition the Linux kernel to rust forces people who already are contributing to go and learn rust to be able to continue what they were already doing. And sure you can argue that it’s being done so not everything has to go over at once, but there is a level of rust knowledge required at the interface between the two languages, and that burden is as far as I’ve seen being forced on those long term contributors.

      It’s not the same thing.

      • arendjr@programming.dev
        7·
        2 months ago

        and that burden is as far as I’ve seen being forced on those long term contributors.

        This is not what is happening. The current long term contributors were asked to clarify semantics about C APIs, so the Rust maintainers could take it from there. At no point were the C maintainers asked to help maintain the Rust bindings.

      • FizzyOrange@programming.dev
        16·
        2 months ago

        Sure, but it’s very similar. The point is that those people didn’t get to choose the language they’re using and now someone is forcing them to use a specific language. They’ve always been forced to use a specific language.

        I guess it just think “I don’t want to learn” is a lame excuse.

        • wewbullEnglish
          23·
          2 months ago

          How about “To learn it to that level will take 10,000 hours I don’t have”? Does that make more sense to you?