Well, yes and no. The surface area for memory-unsafe problems is much smaller, but it&#x27;s still there. To @cheez&#x27;s point, Mirage did contain a very dangerous vulnerability (see <a href="https:&#x2F;&#x2F;www.somerandomidiot.com&#x2F;blog&#x2F;2014&#x2F;07&#x2F;09&#x2F;how-to-set-the-evil-bit&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.somerandomidiot.com&#x2F;blog&#x2F;2014&#x2F;07&#x2F;09&#x2F;how-to-set-t...</a>).<p>I&#x27;m optimistic that long term it&#x27;s a great and obviously worthwhile tradeoff, even though the new stack (and all of <a href="https:&#x2F;&#x2F;nqsb.io" rel="nofollow">https:&#x2F;&#x2F;nqsb.io</a> really) is going to need a lot of real-world usage and examination.<p>Also, size and startup time are definitely pretty cool metrics (or at least fun metrics), and I&#x27;m happy to see both decrease!