That google guy, he's never shipped product..a "researcher".
A quick look at his resume and its just a whole bunch of "research" positions. Not the slightest evidence he has ever shipped actual real life product code. You know, software that people use. Because if he had he would have known that we those of us who do ship system / application code written in C/C++ (and asm) have been using for more than 30 years a whole bunch of tools that do a great job of quickly tracking down all the problems that the YAFL Rust is supposed to fix. Long before DTrace we have tools like SoftICE (back in the 1980's) that could track memory leaks and related unsafe memory usage. Etc.etc. Many many tool.
So yet again its just more Rust spiel written by people who haven't a clue about how software has been developed, validated and shipped in "unsafe" languages like C for the last five decades. Hell, there have even been TXL grammars and scripts for the last 20 years that will do at least 99.99% of job of source code verification for safe memory usages in C and C++. And to sneak through the last 0.01% you have to work very hard at using language tricks.
So just more Rust bollocks from academic kiddie types who cannot be arsed to find out how commercial code has been developed and shipped for many decades. But rather spend time playing with yet another new toy language. Only one high profile end user application has been written in Rust and the result has been catastrophic. Whats Firefoxes market share now? 2%? And almost unusable due to technically incompetent levels of memory resource usage. And this is not the first time a successful product has been destroyed by - Lets rewrite in a completely new language that almost no one uses - either. Thats been going on for many decades too. A rewrite in Modula 2 killed Wordstar back in the 1980's to pick just one example
Biting the hand that feeds IT
