Popular posts

Engineering is all about trade offs. Saying everything should be re-written in Rust is bad engineering. There are valid reasons to keep writing C code. Your project may have one of those. It always depends.

That said, for new projects today, in general, I'd prefer to see them started with Rust than started with C, if all else is equal. It always depends.

Possibly the largest and most well-known C++ project being re-written in Rust is Firefox. Its next release in a few weeks, 57, contains a host of improvements, but one of the ones I'm most excited about is Stylo. It's Servo's CSS handling, but in Firefox. This means that hundreds of millions of people will be using code written in Rust, and I find it thrilling.

To riff off of what Steve said:

one of the ones I'm most excited about is Stylo. It's Servo's CSS handling, but in Firefox. This means that hundreds of millions of people will be using code written in Rust, and I find it thrilling.

This is indeed thrilling, but one of the most interesting things (to me) about Stylo is that it's a great example of how you can integrate Rust into an existing project without rewriting the whole darn thing. Although the Stylo engine is written in Rust, at least in Firefox it's configured to operate over the Gecko DOM, which is all written in C++. If shipping Stylo had required rewriting the DOM, it would never have happened.

(Also, if you've not seen it, Lin Clark's excellent blog post about Stylo is also worth a read.)

Another great security project that's starting to integrate Rust is Tor. They talk about the branch here.