• ProdigalFrog@slrpnk.netOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 month ago

    TL:DW, JPEG is getting old in the tooth, which prompted the creation of JPEG XL, which is a fairly future-proof new compression standard that can compress images to the same file size or smaller than regular JPEG while having massively higher quality.

    However, JPEG XL support was removed from Google Chrome based browsers in favor of AVIF, a standalone image compression derived from the AV1 video compression codec that is decidedly not future-proof, having some hard-coded limitations, as well as missing some very nice to have features that JPEG XL offers such as progressive image loading and lower hardware requirements. The result of this is that JPEG XL adoption will be severely hamstrung by Google’s decision, which is ultimately pretty lame.

        • Telorand@reddthat.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 month ago

          And they’ll make eleventy bajillion dollars in the meantime, plenty of money to pay their inevitable punitive “fines.”

          • TeoTwawki@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            1 month ago

            Hell old MSs penalty was giving free licenses in markets it never had a grip on, so its “lock 'em in!” model meant the “penalty” benefited them!

  • rustydomino@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    Without jpeg compression artifacts how the hell are we supposed to know which memes are fresh and which memes are vintage???

    • booly@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 month ago

      I still think it’s bullshit that 20-year-old photos now look the same as 20-second-old photos. Young people out there with baby pictures that look like they were taken yesterday.

  • cyd@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 month 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?

    • redisdead@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 month ago

      The issue with jpegxl is that in reality jpeg is fine for 99% of images on the internet.

      If you need lossless, you can have PNG.

      “But JPEGXL can save 0,18mb in compression!” Shut up nerd everyone has broadband it doesn’t matter

        • redisdead@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          arrow-down
          1
          ·
          1 month ago

          I have several TBs of storage. I don’t remember the last time I paid attention to it.

          I don’t even use jpeg for it. I have all the raw pics from my DSLR and lossless PNGs for stuff I edited.

          It’s quite literally a non issue. Storage is cheap af.