Well, yes and no. The surface area for memory-unsafe problems is much smaller, but it's still there. To @cheez's point, Mirage did contain a very dangerous vuln

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