I get your enthusiasm, but there are libraries for c that let you use the bounds check instructions in the latest Intel cpu's. (I think there is a pretty good w

I get your enthusiasm, but there are libraries for c that let you use the bounds check instructions in the latest Intel cpu's. (I think there is a pretty good write up about these new instructions on anandtech.) It's not as sexy as a new language but it allows for incremental adoption and doesn't present more effort. Even if it would be a good idea, many people will adopt incremental improvements instead of going for a rewrite. Bounds checking in hardware isn't a new phenomenon, either. The Burroughs had hardware bounds checking, I think. Rust and Go are interesting, I agree. I'm just slightly more suspect about things in tech that have such vocal "evangelism". If they help, that will be seen over time as large projects adopt them. In your effort to make your point you claim that C is "too loose" to take advantage of hardware bounds checking. That kind of thing makes people mistrust the passion that advocates for these languages display. https://en.m.wikipedia.org/wiki/Intel_MPX https://en.m.wikipedia.org/wiki/Intel_MPX