It's both funny and true at the same time.

I used to advertise my worth in how good my C++ is. Until I had a dumb after free error after git merging two adjacent line in the wrong order. A simple vector push done after capturing vector.begin instead of before. Nobody saw that in code review. Even reviews from C++ experts at the company. Of course it took 6 months until the first segfault. Invalidating 6 months of work. Rust would have not compiled. As simple as that.

Now imagine if you could write code without living in fear of making everything blow up because of a single moment of weakness. That's Rust for me.

> Invalidating 6 months of work.

What kind of system was this where a bug would literally invalidate all results from the moment it was introduced?

It’s just another of many testimonials of projects that will not be named at companies that will not be disclosed with implausible circumstances or unlikely details here to convince you that you had better switch your tech stack to this brand new thing before you too become a cautionary tale.

Google. Backup of filers. Conversion from NetApp filer dumps to tarball. I did open source a prototype of the tool. I don't know if it has the bug. The final version was to Google standard of C++ and maybe some cleaner abstractions. https://github.com/bombela/dump2tar

It would be funny if they couldn't cite an endless stream of evidence for their argument. They can, however.

And it's not going to stop. That's the thing about the memory safety argument; the people making it have an endless supply of ammunition, resupplied daily.

See: https://twitter.com/LazyFishBarrel

These people are obviously serious.