Yeah, I agree, and I like C!
I think the lack of bounds checks where they are not a problem is a massive design flaw nowadays. Zig should have made bounds checks universal and spent effort on compiler passes to elide them.
Allowing people to remove bounds checks is not smart (though Rust's unsafe is a good compromise), especially in such a coarse way as a build option.
In fact, a supposedly memory-safe language, Julia, has memory bugs because it allows users to turn bounds checks off. [1] This should never have happened.
On my experience, only small teams with top devs do happen to care for doing the security work you describe, as tends to be proven by surveys regarding the use of unit testing or static analysis tooling,
https://www.jetbrains.com/lp/devecosystem-2021/c/
https://www.jetbrains.com/lp/devecosystem-2021/cpp/
So yeah, pity that memory-safe languages have to fight back to regain what was already possible before UNIX took over the computing world and brought C for the ride.
This is why I would like that Zig could offer more than Modula-2 already did in 1978, in regards to memory corruption.