4 ms·
> Increasing productivity: Safe Coding improves code correctness and developer productivity by shifting bug finding further left, before the code is even checke
by benwilber0 2y ago
> Increasing productivity: Safe Coding improves code correctness and developer productivity by shifting bug finding further left, before the code is even checked in. We see this shift showing up in important metrics such as rollback rates (emergency code revert due to an unanticipated bug).
> The Android team has observed that the rollback rate of Rust changes is less than half that of C++.
I've been writing high-scale production code in one language or another for 20 years. But I when I found Rust in 2016 I knew that this was the one. I was going to double-down on this. I got Klabnik and Carol's book literally the same day. Still have my dead-tree copy.
It's honestly re-invigorated my love for programming.
- pclmulqdq 2y agoThat makes sense because the #1 reason I have had to roll back my own C++ commits is due to crashes from some dumb failure to check whether a null pointer is null. If Rust is going to prevent that issue and other similar issues of stupid coding, you would expect whole classes of rollbacks to go away.
- acdha 2y agoI now compare C to an IKEA bed we have in our guest room which has storage drawers making the edge straight down to the floor without a gap. I’m a grownup, I know that I need to stop half a step early, but every few weeks I stub a toe while I’m thinking about something else.
- ahoka 2y agoTBH most of these issues go away when your language has no implicit nullability.
- steveklabnik 2y agoThat’s very kind, thank you.
- selfmodruntime 2y agoI feel entirely the same. I actively miss Rust when I need to choose another language.
- benwilber0 2y agoYou're a legend. Thanks for writing The Book. It really affected my life in a very positive way.
- deleted 2y ago[deleted]