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.

  • GetOffMyLan@programming.dev
    link
    fedilink
    arrow-up
    8
    ·
    edit-2
    3 months ago

    I mean I’ve still yet to hear a reason not to use rust tbf.

    But yes that’s what working in a team is like.

    I have to do stuff at work so I don’t fuck over the frontend team. I don’t throw a little tantrum about it.

    • PushButton@lemmy.world
      link
      fedilink
      arrow-up
      3
      arrow-down
      7
      ·
      edit-2
      3 months ago

      Badgering

      I mean I’ve still yet to hear a reason not to use rust tbf.

      You can’t take NO as an answer, don’t you?

      That’s bad attitude

      Linux is not “work”; you surely don’t grasp the reality of the situation here.

      And “tbf”, the incessant pushing of Rust from people like you is a perfectly fine reason to not use Rust…