> It turns out that long before memory-safety had become a fashionable topic at tinder dates, the problem had been identified and attacked by a programming language called Seed7. "Long before" as in three decades ago. "Attacked" in surprisingly lean ways.
> When I first stumbled upon it earlier this year, the combination of static typing with interpreted execution caught my interest. Programs can also be compiled, thereby attaining performance in the ballpark of C. My curiosity was further piqued by its proclaimed memory safety without employing a garbage collector. I wondered, hasn't this been the key innovation and unique selling point of Rust's borrowing concept? How can a language rooted in the late 80s make such claims?
> There is hardly anything as stimulating to me as dwelling in the creations of a mind with an exceptionally fine taste.
> It turns out that long before memory-safety had become a fashionable topic at tinder dates, the problem had been identified and attacked by a programming language called Seed7. "Long before" as in three decades ago. "Attacked" in surprisingly lean ways.
> When I first stumbled upon it earlier this year, the combination of static typing with interpreted execution caught my interest. Programs can also be compiled, thereby attaining performance in the ballpark of C. My curiosity was further piqued by its proclaimed memory safety without employing a garbage collector. I wondered, hasn't this been the key innovation and unique selling point of Rust's borrowing concept? How can a language rooted in the late 80s make such claims?
> There is hardly anything as stimulating to me as dwelling in the creations of a mind with an exceptionally fine taste.