The Android team has observed that the rollback rate of Rust changes is less than half that of C++.
11 Likes
Jonathan Perkin's reply when he was asked why he chose to write mktool in Rust [over C]:
I'm the wrong side of 45. I have zero interest in wasting any time that I might have left writing C from scratch. Writing Rust is pure joy. I can go from an idea to a working, tested, robust, published and packaged implementation in the time it would take me to even begin the first few lines of a C version. The tooling is beautiful, makes programming fun, and the end result usually outperforms the equivalent C. Once it builds I know it will run perfectly on all of the platforms I care about, and I don't have to go around manually testing on them to find all of the various platform and compiler quirks that will break it.
11 Likes
It was 10 days ago, but I was late in noticing this:
The Rust programming language feels like a first generation product.
It feels like the other way around to me. A first-generation product is pure, clean, an unblemished view of the developerâs view of how the world works (or how they want it to). Then you get a couple years in and the weird edge cases start popping up, as reality asserts itself.
All the fussy, weird, difficult-to-explain parts of Rust are signs that itâs v2 (or vâŚ300?) of the product series called âlanguages that let you write kernel drivers that wonât crash as oftenâ.
4 Likes