• DrakeAlbrecht@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      Boynton also calls out the sheer number of fixes in WebKit, which he calls “one of the largest attack surfaces on the platform.”

      It wouldn’t be, if Apple would allow other browsers to use their own rendering engines.

        • egregiousRac@piefed.social
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          With everybody on Webkit, a vulnerability in it applies to every browser and nearly all apps on iOS. If other engines were allowed, a threat would only apply to apps using that engine.

          On the flip side, keeping the engine centralized means that a single fix will close a hole in every app, keeping unmaintained apps safer.

          • Em Adespoton@lemmy.ca
            link
            fedilink
            English
            arrow-up
            0
            arrow-down
            1
            ·
            3 months ago

            I wonder if it would be possible to implement Firefox or Chromium in webassembly and run it on top of WebKit — it wouldn’t be as performant, but would be an extra layer of sandbox. You could theoretically do this in any app that uses WebKit too.