1. 7

previous thread

  1.  

  2. 2

    This was first released in 2013

    1. [Comment removed by author]

      1. 1

        It’s basically Software Fault Isolation using obsolete method (Chrome’s). Those older methods traded off security in favor of performance which led to breaks. CompSci has much better stuff these days. Just need more labor put into it.

        1. [Comment removed by author]

          1. 2

            It’s not so much flaky as a risky choice due to tradeoffs. They lowered the security to help on their goal of being fastest browser. Stronger stuff just had a heavier effect on development time or performance. Cutting-edge stuff today, depending on tradeoffs, has less negatives on those for similar level of security. Rust or Code Pointer Integrity are illustrative examples on fast stuff side with Softbound+CETS or Data Flow Integrity being heavier stuff.