• Aatube@kbin.social
    link
    fedilink
    arrow-up
    1
    arrow-down
    3
    ·
    edit-2
    1 year ago

    That’s not the reason; Safari and the like still support the WebExtensions API (the same the Firefox uses). They just require extensions to be signed, .app’d, distribute through App Store etc. and maybe only go to Safari which is a lot.

    • TrickDacy@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I read this over and over and it makes no sense to me. Even if you were right, do we really think that FF extension devs are going to make and maintain a completely separate codebase for a iOS-only FF version of each extension? I highly, highly, doubt anyone would do that.

      Then on top of it, yeah, maybe you’d have to kiss Apple’s ass to ever get it installed on a user’s device. In any case, Fuck apple with a cactus.

      • Aatube@kbin.social
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        It’s the same codebase. Safari can use extensions written for Firefox as long as you compile it into Apple format.

        • TrickDacy@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Bizarre. All these years, every time I have tried to use a safari extension, even very popular ones like 1password, I’ve had issues. So I feel like it’s historically not been as simple as this… Maybe it is now, but all the web devs I know HATE safari. Myself included.

          • Aatube@kbin.social
            link
            fedilink
            arrow-up
            1
            ·
            1 year ago

            I mean, you’ve still got the entire signing BS so there is a very valid reason to hate.