• ViatorOmnium@piefed.social
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    2
    ·
    edit-2
    7 days ago

    Congratulations, your noob user is now using JPEG-XL. It’s not working on old devices, or any mainstream browser besides Safari. The less mature library also has a bug that allows for RCE and now everyone is running a cryptominer.

    Now you say, but webp is supported everywhere, so let’s go with that. Now the noob is using wepb for a bunch of rasterised vector graphics with 4 or 5 flat colors, and he’s wasting more disk space than before.

    So I repeat, if you need one size fits all, PNG is better, it works everywhere, and it’s even more efficient in cases where lossless graphics matter the most.

    • comfy@lemmy.ml
      link
      fedilink
      arrow-up
      11
      ·
      edit-2
      7 days ago

      Now the noob is using wepb for a bunch of rasterised vector graphics with 4 or 5 flat colors, and he’s wasting more disk space than before.

      I just tested with this image:

      Default GIMP WebP export settings (90% quality): 88.8 kB

      Lossless WebP mode: 85.6 kB

      Default GIMP PNG export settings (compression level 9): 189.8 kB

      So I don’t trust this claim unless you have some evidence.

      • Ferk@lemmy.ml
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 day ago

        It’s ironic how WebP lossless mode is actually better at compressing the image than the lossy mode.

        I bet most people would use the default thinking that they are making a compromise and that increasing the quality would make the compression worse. They wouldn’t know unless they tested making the images themselves, because it’s not easy for users to differentiate lossy webp from lossless webp.

        This imho is why lossless should be in its own format, instead of trying to make a single container format do everything like WebP was trying. A new compression level for PNG would be most welcome.