&gt; You consider software complexity comparable at a broader level than I do.<p>If you&#x27;re currently starting your career in software, you&#x27;re sure to -one day- consider the topic in the same way that I do. It&#x27;s the only rational way to think about it.<p>Regardless of how you think about the comparability of software complexity between software projects, your statement about the near-impossibility of creating <i>correct</i> complex software was a gross overstatement; one that you&#x27;re <i>still</i> not owning up to. :)<p>That bug list is not a list of CVEs. What&#x27;s more, it&#x27;s a list of bugs for the <i>entire</i> Chromium project. I assume that you <i>couldn&#x27;t</i> find any CVEs that only affected V8 the JS engine, as used in Chrome or Chromium. Their absence shoots a really big hole in the foundation of your primary claim, which was: &quot;[There exists no] functional browser that doesn&#x27;t have bunches and bunches of exploitable bugs in its JS engine.&quot;.