Please read the quotation more carefully. I appreciate the author calls out the source of the data, but the claims remain overly strong, broad and unqualified.
I concede this may not be the strongest example, but in my opinion, the language throughout the article, starting with the title, makes stronger claims than the evidence provided supports.
I agree with the author, that these are useful projects to use for research. I'm struggling with the lack of qualification when it comes to the conclusions.
Perhaps I missed it, but I also didn't see information about trade-offs experienced in the transition to Rust on these projects.
Was there any change related to other kinds of vulnerabilities or defects?
How did the transition to Rust impact the number of features introduced over a given time period?
Were the engineers able to move as quickly in this (presumably) new-to-them language?
I'm under the impression that it can take many engineers multiple years to begin to feel productive in Rust, is there any measure of throughput (even qualitative) that could be compared before, during and after that period?
I'm hung up on what reads as a sales pitch that implies broad and deep benefits to any software project of any scope, scale or purpose and makes no mention of trade offs or disadvantages in exchange for this incredible benefit.