• cyd@lemmy.world
    link
    fedilink
    English
    arrow-up
    49
    ·
    4 months ago

    People are quick to blame Google for the slow uptake of Jpeg XL, but I don’t think that can be the whole story. Lots of other vendors, including non-commercial free software projects, have also been slow to support it. Gimp for example still only supports it via a plugin.

    But if it’s not just a matter of Google being assholes, what’s the actual issue with Jpeg XL uptake? No clue, does anyone know?

    • Skeletonek@lemmy.zip
      link
      fedilink
      English
      arrow-up
      38
      ·
      4 months ago

      GIMP supports JPEG XL natively in 3.0 development versions. If I remember correctly GIMP 2.10 was released before JPEG-XL was ready, so I think that’s the reason. They could have added support in smaller update though, which was the case with AVIF.

    • tal@lemmy.today
      link
      fedilink
      English
      arrow-up
      29
      ·
      edit-2
      4 months ago

      Lots of other vendors, including non-commercial free software projects, have also been slow to support it.

      checks

      It doesn’t look like the Lemmy Web UI supports JPEG XL uploads, for one.

    • Aux@lemmynsfw.com
      link
      fedilink
      English
      arrow-up
      2
      ·
      4 months ago

      The problem with XL is that it has way too many features. HDR, for example. Firefox doesn’t support HDR at all, Chrome added HDR image (not video) support just late last year. And that’s just one feature of XL… Even if both Google and Mozilla will start actively working on support we won’t see anything useful for a few years. And then how do you even create images in the first place?