• 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

  • drkt@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    108
    arrow-down
    4
    ·
    9 months ago

    I’m a photographer; AVIF and WebP do not serve my needs, JPEG-XL does.

    I run my own website down to the hardware in my living room; I will not store 5 variations of any 1 picture just so I can serve the best available to clients when JPEG works everywhere and JPEG-XL offers me a lossless transition from JPG to JXL.

    Chromium is literally the only reason JPEG-XL isn’t being adopted right now, and it’s so obvious that Google is pulling those strings.

    JPEG-XL Ride or Die.

    • Potatos_are_not_friends@lemmy.world
      link
      fedilink
      English
      arrow-up
      38
      arrow-down
      1
      ·
      edit-2
      9 months ago

      Mozilla has not jumped on the JPEG XL bandwagon either: The Firefox maker said it’s neutral with regard to the technology, citing cost and lack of significant differentiation from other image codecs.

      Two browser orgs.

      Not arguing just pointing it out

      • drkt@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        25
        ·
        9 months ago

        Mozilla are also dumb, yes, but they aren’t the one in control of 90% of the browser marketshare.

      • Turun@feddit.de
        link
        fedilink
        English
        arrow-up
        16
        ·
        9 months ago

        There is a difference between indifference and actively working against something.

    • ILikeBoobies@lemmy.ca
      link
      fedilink
      English
      arrow-up
      31
      ·
      9 months ago

      I saw a web warning saying “if you cant see {x} then consider upgrading to Firefox” today and it fill me with joy

    • abhibeckert@lemmy.world
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      10
      ·
      edit-2
      9 months ago

      Why do you need to transition from jpeg to anything else? Just keep using jpeg for old files.

      Chromium is literally the only reason jpeg-xl isn’t being adopted right now

      That’s not a “reason” it’s a “decision”. Their actual reason is pretty good — they don’t want to support every image format that comes along. That’s a slippery slope, there are several hundred image formats - should they all be supported? How many of them have security flaws? How much work is it to check for security flaws even if none exist?

      The original image formats for the web, jpeg, gif, png, svg, all have major benefits compared to each other. That’s why they were successful. There used to be other widely used image formats but they all fell by the wayside because the goal is to try not to have many formats. Ideally we’d only have one.

      And WebP moves a long way in that direction, it does basically everything except vector images. AVIF is still around for efficiency reasons (it’s very really easy/fast/low battery consumption for camera hardware to create an AVIF).

      JPEG-XL has advantages but unlike those two they are really small and not worth the effort.

      • Turun@feddit.de
        link
        fedilink
        English
        arrow-up
        21
        ·
        9 months ago

        Converting from jpeg to jxl comes some serious space savings and can be done losslessly.

        The original image formats for the web, jpeg, gif, png, all have major benefits compared to each other. That’s why they were successful.

        We change video formats without any major benefits of one over the other. I think it’s totally reasonable to do the same with image formats. Especially the data can be losslessly compressed even more.

        I wouldn’t call speed a major factor for image processing anyway. It’s hugely important for movies, where AVIF is coming from, but much less so when there is no hard 30x2160x3840 pixels/s benchmark you need to reach.

      • drkt@lemmy.dbzer0.com
        link
        fedilink
        English
        arrow-up
        12
        ·
        9 months ago

        Just keep using jpeg for old files.

        And bloat up my codebase with support for a new file extension every 2-5 years? I’ll just keep using jpg, then, like the rest of the sane internet, and the format will never die. JXL offered an actual upgrade path, webp and avif doesn’t.

      • TherouxSonfeir@lemm.ee
        link
        fedilink
        English
        arrow-up
        7
        arrow-down
        1
        ·
        9 months ago

        They do run a physical machine in their living room for their website… for some reason…