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.

  • GetOffMyLan
    4·
    2 months ago

    I guess you can argue it’s already written in C. So that was always a requirement.

    • ladEnglish
      41·
      2 months ago

      That way we’ll just find maintainers went near extinct over time, just like COBOL developers that are as rare as they are expensive. Only Linux kernel isn’t a bank, and maybe will not have as much money to pay to rare developers capable of maintaining C codebase

      • lysdexicEnglish
        12·
        2 months ago

        That way we’ll just find maintainers went near extinct over time, just like COBOL developers that are as rare as they are expensive.

        Care to take a shot at figuring out why COBOL is still used today?

        I mean, feel free to waste your time arguing for rewrites in your flavor of the month. That’s how many failed projects start, too, so you can have your shot at proving them wrong.

        But in the meantime you can try to think about the problem, because “rewrite it in Rust” is only reasonable for the types who are completely oblivious to the realities of professional software development.

        • ladEnglish
          2·
          2 months ago

          It’s used because the ones who use it have enough money to pay for any problems that may arise from it’s use, and known problems are deemed better than unknown ones.

          It is a viable model when you have enough money and resources, but a conservative one

          • lysdexicEnglish
            11·
            2 months ago

            It’s used because the ones who use it have enough money to pay for any problems that may arise from it’s use, (…)

            That’s laughable. Literally the whole world uses it. Are you telling me that everyone in the world just loves to waste money? Unbelievable.

            • ladEnglish
              2·
              2 months ago

              Have you ever worked at large old corporation? Wasting money is a bit of an underestimation on that scale.

              Also, not all banks use COBOL, but the ones that don’t are usually much younger.

              Besides, Ada would’ve been a better example, as it is used by telecoms and seems to be held in high regard, unlike COBOL. The only issue with Ada I heard of is that it’s on par with C++ in complexity which is far from being simple.

              • lysdexicEnglish
                1·
                2 months ago

                Have you ever worked at large old corporation?

                I’m not sure you understand that it’s way more than “large old corporations” that use it. Everyone uses it, from large multinationals to small one-taxi shops, and even guys like you and me in personal projects. This has been going on for years. I really don’t know what led you to talk about large old corporations, seriously.

                • ladEnglish
                  1·
                  2 months ago

                  Are we still talking about COBOL?