Earlier quoted context omitted.
FWIW C++ can do bound checks aka hardened STL. On the other hand google did riir some of their programs and removed bound checks there for speed, welcome to real world, so absence of bound checks is not a mistake, but an intended performance goal.
Google is consciously making Chrome less secure because otherwise the performance is unacceptable. The end result is about 300 CVEs every year for the last 10 years. That's for an almost 20 year old project that had most of its security issues resolved very early on. And you're saying somebody who is not Google can make a brand new browser engine from scratch in 2026, have it perform good enough to be actually usable…
Also modern standard compliant (without adblock) browsers don't perform anywhere good.