Fans of the spec bemoan lack of transparency in Interop 2024 process
  • Browser makers Apple, Google, Microsoft, and Mozilla have announced Interop 2024, a project to promote web browser interoperability.
  • JPEG XL, a potential replacement for JPEG and PNG image formats, was not included in Interop 2024.
  • The rejection of JPEG XL has been blamed on Google, with the Google Chrome team deciding not to support the image compression technology.

Archive link: https://archive.ph/nulY6

  • RayJW@sh.itjust.worksEnglish
    74·
    9 months ago

    I still won’t get over it and will keep fighting for JPEG XL. It would fix so many issues and greatly reduce the bandwidth need of the internet while not either having weird licensing or royalties and / or being a „what if we just took one frame from a video“ picture format. Also it can encode back to JPEG lossless for legacy uses. What more could one want?

    • Dark Arc@social.packetloss.ggEnglish
      222·
      9 months ago

      I mean there are advantages to using AV1 for photos… Hardware accelerated decoding being one.

      Decoding a large AVIF image grid should in theory work on a GPU and happen faster with less power than any software based image format implementation.

      AV1 is also just an awesome format that’s entirely free to use out of the gate.

      • RayJW@sh.itjust.worksEnglish
        19·
        9 months ago

        Well yes, however without acceleration JPEG XL is many times faster. Also if you only have a CPU for example.

        It’s also highly parallelizable compared to AVIF which also matters a lot considering the amount of cores is growing with the likes of ARM and hybrid architecture CPU.

        AVIF also fairs badly with high fidelity and lossless encoding, has 1/3 the bit depth and pretty small dimension limits for something like photography.

        I don’t think AVIF is per se a bad format. I just think if I want to replace a photo oriented format I’d like to do that with one that’s focused on „good“ photos and not just an afterthought with up- and downsides.

        • QuaternionsRock@lemmy.worldEnglish
          41·
          9 months ago

          Also if you only have a CPU for example.

          I thought even mobile-tier integrated GPUs can decode AV1 extremely quickly.

          • RayJW@sh.itjust.worksEnglish
            5·
            9 months ago

            Well yes sure, but remember AV1 decoding only became standard like 1-2 GPU generations ago. Encoding only this generation. iPhones only got support with the 15 Pro so it will be another generation before it trickles down to the base models. And what about the hundreds of millions of Android phones in Asia and the likes with dirt cheap SoCs. Pretty sure they don’t have dedicated AV1 decoding hardware for a long time.

            So that’s a TON of hardware being made slow and inefficient if everything were to be AVIF tomorrow. Not saying AVIF decoding will be a big hurdle in the future but how long until all this hardware browsing the web has been replaced? That’s why I think somethings that’s efficient and fast on CPUs without any specialised hardware is more suited for a replacement.

          • anlumo@lemmy.worldEnglish
            4·
            9 months ago

            Servers often come without GPU, and they’re usually the ones encoding image formats.

            • QuaternionsRock@lemmy.worldEnglish
              1·
              9 months ago

              I don’t think we should worry about servers meant for image transcoding not having the proper hardware for image transcoding. The problem with the GPU requirement starts and ends with consumer devices imo