Borrow Checking, RC, GC, and the Eleven (!) Other Memory Safety Approaches

> Imagine my surprise when the customers chief software engineer said "Of course it leaks". He went on to point out that they had calculated the amount of memory the application would leak in the total possible flight time for the missile and then doubled that number.

This is the funniest "feature, not a bug" explanation I've ever seen.