The “Manifest V3” rollout is back after letting tensions cool for a year.

  • Admiral Patrick@dubvee.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    10 months ago

    Tell me about it. Every time I implement some new thing in my app:

    Firefox/Chrome: You cast HTML5 video. Critical hit!

    Safari: Your spell fizzles…

    • anlumo@feddit.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      10 months ago

      It also took 6 years longer than everybody else to support WebGL2, and it’s the only browser without a working WebGPU implementation. It also has no timeline for wasm-gc, while Chrome already ships with it default enabled and Firefox will ship with it on the next release.

      • abhibeckert@beehaw.org
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        10 months ago

        It also has no timeline for wasm-gc

        Apple has been removing support for garbage collection from other technologies that used to support it. Wouldn’t be surprised if they never add support for that, they’ll tell you not to waste CPU cycles (and therefore, battery power) collecting garbage.

        They want you to figure out when memory should be deallocated at compile time, not run time.

        • anlumo@feddit.de
          link
          fedilink
          English
          arrow-up
          0
          ·
          10 months ago

          I personally prefer to use such languages, but I often don’t have a choice for certain tech stacks.