• hedgehog@ttrpg.network
    link
    fedilink
    English
    arrow-up
    1
    ·
    3 months ago

    Compared to something like JPEG XL? [PNG] is hands down worse in virtually all metrics.

    Until we circle back to “Jpeg XL isn’t backwards compatible with existing JPEG renderers. If it was, it’d be a winner.”

    APNG, as an example, is backwards compatible with PNG.

    If JPEG-XL rendered a tiny fallback JPEG (think quality 0 or even more compression) in browsers that don’t support JPEG-XL, then sites could use it without having to include a fallback option themselves.

    • KairuByte@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 months ago

      Why are you using PNG when it’s not backwards compatible with gif? They don’t even render a small low quality gif when a browser which doesn’t support it tries to load it.

      • hedgehog@ttrpg.network
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 months ago

        Are you seriously asking why a commonly supported 27 year old format doesn’t need a fallback, but a 2 year old format does?

        • KairuByte@lemmy.dbzer0.com
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          When png was released, it was unsupported by the majority of browsers (and is still not supported by everything mind you) but didn’t have a fallback to a more widely adopted format. It was finalized 9 years after gif, which admittedly is a third of the gap between now and png finalization.

          Fallback support isn’t needed. It never has been before, why would it suddenly be needed now? Servers are more than capable of checking the browser on request and serving a different format based on that. They’ve been capable of doing that for decades, and the effort that goes into it is virtually non existent.