It's dumb that in 2017 the author doesn't say anything specific about Rust, which is by far the strongest "C replacement" candidate. The author doesn't deal wi

It's dumb that in 2017 the author doesn't say anything specific about Rust, which is by far the strongest "C replacement" candidate. The author doesn't deal with the problem that the "direct access to memory without abstractions" style they love so very easily drifts into undefined behaviour. It also optimizes very poorly due to lack of aliasing information, unless you enable type-based alias analysis in which case accidental undefined behavior is catastrophic. The "dynamically checked C" they propose as a solution to C's safety issues is no solution at all until you can get it to work in practice. A lot of really great people, including the researchers he cites, have tried really hard to make it work and have failed in practice. He doesn't seem to understand why they failed or have any insight into how to overcome the problems.