Programming

17008 readers

368 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

175

Google says replacing C/C++ in firmware with Rust is easy (www.theregister.com)

submitted 1 week ago by lemmee_in@lemm.ee to c/programming@programming.dev

94 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] nickwitha_k@lemmy.sdf.org 4 points 1 week ago (5 children)

If the target for the firmware has stdlib already implemented, my experience has been that it is indeed easy with minimal experience in the language.

[–] 0x0@programming.dev 32 points 1 week ago (4 children)

Mixing "firmware" with "easy with minimal experience" in the same sentence makes me cringe...

[–] nickwitha_k@lemmy.sdf.org 13 points 1 week ago (2 children)

That's fair. To be clear, I meant minimal experience with the Rust programming language. I've mainly tinkered with ESP32 types of MCUs in Arduino and CircuitPython when it comes to firmware, but have much more software experience. In some ways, I found the little bit of Rust that I tried easier because of the tooling - defaulting to a CLI tool to flash rather than an IDE is much more comfortable for me.

[–] towerful@programming.dev 1 points 1 week ago (1 children)

I've been meaning to play with rust, and I've always enjoyed tinkering with various MCUs... Although I'm not very strong with firmware/embedded programming.

Do you think programming an ESP32 is a good project for learning rust?
Any suggested place to start? (Tutorials, YouTube Vida etc)

[–] nickwitha_k@lemmy.sdf.org 2 points 6 days ago

Do you think programming an ESP32 is a good project for learning rust?

I've only barely scratched the surface there myself but, I absolutely do think so. For several reasons. First, ESP32 is one of the few series of MCUs that support the Rust stdlib. And learning what that entails for Rust is extremely helpful in conceptualizing build targets. Second, MCUs are a very constrained target for software/firmware. Getting comfortable there will likely improve your code efficiency in other code platforms as you are more likely to think about resource usage earlier. And third, there's some pretty excellent docs and tutorials.

Any suggested place to start? (Tutorials, YouTube Vida etc)

For tutorials, my recommended starting point is with the official docs/books themselves:

load more comments (1 replies)