> Assuming Chrome is rewritten in Rust or Go, will these security
  > issues vanish? Of course not

It's true that they will never _vanish_, but all of the ones related to memory safety, which are the ones the article focuses on, shouldn't happen in Rust:

  > 70% of the high-risk bugs in Chrome 44 would have been prevented
  > if Chrome were written in a memory-safe language instead of C/C++.

(it's true that it's not 100%, because someone could still write bad code in an unsafe block, but that's a _significant_ reduction in the surface area, which should lead to a similar reduction in errors.)