More evidence that memory safety is the future for programming languages

[Johan]

On Saturday, 28 March 2020 at 20:24:02 UTC, Walter Bright wrote:
> https://news.ycombinator.com/item?id=22711391
>
> Fitting in with the push for @safe as the default, and the 
> @live Ownership/Borrowing system for D.
>
> We can either get on the bus or get run over by the bus.

Why is this news?
Clang has had this for a decade, and it certainly wasn't the 
first. If there is a bus, it's left the station a very long time 
ago.

Isn't it more interesting to find a comprehensive resource 
management solution, instead of working on a solution only for 
the special case of memory [*]. A double file close is also bad, 
for example.
Maybe RAII and move semantics isn't it, but at least it doesn't 
single out one type of resource.

-Johan

[*] Let alone the even more special case of functions with the 
exact symbol names "malloc" and "free" in this case...