1 comment

sorted by: hot top controversial new old
[–] 10 points 1 year ago

TLDR: now supports

  • HDR
  • Animated PNG files
  • Exif data
  • source
  • 46 comments in c/programming@programming.dev view that post
    [–] 51 points 1 year ago (7 children)

    I didn't realize it had gone anywhere. It's always my first choice.

  • source
  • hideshow 7 child comments
  • [–] 41 points 1 year ago (6 children)

    WebP had been kind of moving in on its turf, based on what I've been seeing websites using.

  • source
  • parent
  • hideshow 6 child comments
  • [–] 3 points 1 year ago (5 children)

    I've never heard of webP. Looked it up. Not impressed. Sticking with png.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 23 points 1 year ago (2 children)

    The main advantage of webp is that it has good lossy compression, which makes it great for websites that show tens or hundreds of images on a single page

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 1 year ago (1 child)

    I always used PNG where I would have used GIF. Other than that I use JPG still. I'm guessing webp is more on the JPG side of things than the GIF side?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 3 points 1 year ago

    It can do both, lossiness is toggleable.

    If you've seen a picture on Lemmy, you've almost certainly seen a WebP. A fair bit of software – most egregiously from Microsoft – refuses to decode them still, but every major browser has supported WebP for years and since superior data efficiency compared to JPG/PNG means is already very widely used on the web. Bandwidth is not that cheap.

  • source
  • parent
  • [–] 27 points 1 year ago (3 children)

    Um, actually it's pronounced png

  • source
  • hideshow 3 child comments
  • [–] 98 points 1 year ago (5 children)

    Great news! PNG has always been my image format of choice due to its relatively good compression and support for transparency.

  • source
  • hideshow 5 child comments
  • [+] 9 points 1 year ago (2 children)
  • [–] 75 points 1 year ago* (1 child)

    PNG has terrible compression

    It's fine if you're using it for what it's intended for, which is images with flat color or an ordered dither.

    It's not great for compressing photographs, but then, that wasn't what it was aimed at.

    Similarly, JPEG isn't great at storing flat-color lossless images, which is PNG's forte.

    Different tools for different jobs.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 39 points 1 year ago*

    JPEG isn't great at storing flat-color lossless images, which is PNG's forte.

    JPEG isn’t, but JPEG-XL, on the other hand, has come into existence and has great compression while being pixel-perfect lossless as compared to PNG (among a host of other improvements).

    If only it got the support it deserves (thanks Google for making that harder)

  • source
  • parent
  • [–] 13 points 1 year ago*

    Did it go away? I still use it as my go to format for small lossless images.

  • source
  • [–] 22 points 1 year ago* (last edited 1 year ago) (4 children)

    What's next?

    I know you all immediately wondered, better compression?. We're already working on that. And parallel encoding/decoding, too! Just like this update, we want to make sure we do it right.

    We expect the next PNG update (Fourth Edition) to be short. It will improve HDR & Standard Dynamic Range (SDR) interoperability. While we work on that, we'll be researching compression updates for PNG Fifth Edition.

    One thing I'd like to see from image formats and libraries is better support for very high resolution images. Like, images where you're zooming into and out of a very large, high-resolution image and probably only looking at a small part of the image at any given point.

    I was playing around with some high resolution images a bit back, and I was quite surprised to find how poor the situation is. Try viewing a very high resolution PNG in your favorite image-viewing program, and it'll probably choke.

    • At least on Linux, it looks like the standard native image viewers don't do a great job here, and as best I can tell, the norm is to use web-based viewers. These deal with poor image format support support for high resolutions by generating versions of the image at multiple pre-scaled levels and then slicing the image into tiles, saving each tile as a separate image, so that a web browser just pulls down a handful of appropriate tiles from a web server. Viewers and library APIs need to be able to work with the image without having to decode the whole image.

      gliv used to do very smooth GPU-accelerated panning and zooming


    I'd like to be able to do the same for very high-resolution images, decoding and loading visible data into video memory as required.

    • The only image format I could find that seemed to do reasonably well was pyramidal TIFF.

    I would guess that better parallel encoding and decoding support is likely associated with solving this, since limiting the portion of the image that one needs to decode is probably necessary both for parallel decoding and for efficient high-resolution processing.

  • source
  • hideshow 4 child comments
  • [+] 2 points 1 year ago (1 child)
  • [–] 7 points 1 year ago

    Again, that would be TIFF. TIFF images can be encoded either with each line compressed separately or with rectangular tiles compressed separately, and separately compressed blocks can be read and decompressed in parallel. I have some >100GiB TIFFs containing elevation maps for entire countries, and my very old laptop can happily zoom and pan around in them with virtually no delay.

  • source
  • parent
  • load more comments (-1 replies)
    [–] 10 points 1 year ago (4 children)

    APNG wasn't officially part of the spec?!

  • source
  • hideshow 4 child comments
  • [–] 21 points 1 year ago

    Crazy huh but APNG was so well done it just showed the first frame like a normal PNG in any non supported browser which was amazing. I used to have an avatar which has the TF2 engineer as the first frame and the spy as the second.

  • source
  • parent
  • [–] 6 points 1 year ago (2 children)

    I'm glad it is now. I remember a decade or so ago, I wrote an APNG decoder, so I was deep in the world of APNG.

    And I remember reading various things that made me think MNG was the 'more official' flavour of "animated PNG", and it was absurd to me, because APNG seemed like a much more approachable spec. I'm glad the winds have turned...

  • source
  • parent
  • hideshow 2 child comments
  • [–] 5 points 1 year ago (1 child)

    I remember MNG and never understood why APNG wasn't officially recognized. I didn't know it was widely supported already. Why do people still create and use GIF in the internet, if there is a superior format?

  • source
  • parent
  • hideshow 1 child comment
  • [–] 7 points 1 year ago*

    At least at one point, GIF89a (animated GIF) support was universal among browsers, whereas animated PNG support was patchy. Could have changed.

    I've also seen "GIF" files served up online that are actually, internally, animated PNG files, so some may actually be animated PNGs. No idea why people do that.

  • source
  • parent
  • [–] 14 points 1 year ago

    HDR PNG is huge

  • source
  • [–] 12 points 1 year ago*

    Yes. But does Lemmy support .png?

    Ahh.

  • source
  • [–] 6 points 1 year ago

    Good. Kill webp and its incompatible ass.

  • source
  • [–] 5 points 1 year ago

    Took me a second to realise you're not talking about Papua New Guinea.

  • source
  • [–] 9 points 1 year ago (4 children)

    Possibly the final version. Quite Okay Imaging (QOI) achieved similar compression with none of the complexity. Lossy + difference = lossless formats are surely the better option where performance is not crucial. Even the fact they fffucking finally made APNG official is decades late to replace GIF, since several image formats are now literally video formats.

    The future is webp. And telling software patents to burn in hell.

  • source
  • hideshow 4 child comments
  • [–] 26 points 1 year ago (3 children)

    The future is webp JPEG XL...

    And telling software patents to burn in hell.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 12 points 1 year ago (6 children)

    May webp die a horrible death in its wake!

  • source
  • hideshow 6 child comments
  • [–] 5 points 1 year ago (3 children)
  • [–] 7 points 1 year ago* (2 children)

    Because most of my software doesn’t have support for webp, including but not limited to my Mac, phone, and messaging apps. Until everything supports it, I have to keep converting it to use it, so I just don’t bother saving anything as webp. In fact, I have a firefox extension that lets me save webp as other image formats.

    It may be good to use for the web, but it’s not yet good for me.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 1 year ago* (last edited 1 year ago)

    On the "better compression" front, I'd also add that I doubt that either PNG or WebP represent the pinnacle of image compression. IIRC from some years back, the best known general-purpose lossless compressors are neural-net based, and not fast.

    kagis

    https://fahaihi.github.io/NNLCB/

    These guys apparently ran a number of tests. They had a neural-net-based compressor named "NNCP" get their best compression ratio, beating out the also-neural-net-based PAC, which was the compressor I think I recall.

    The compression time for either was far longer than for traditional non-neural-net compressors like LZMA, with NNCP taking about 12 times as long as PAC and PAC taking about 127 times as long as LZMA.

  • source
  • 12 comments in c/technology@lemmy.ml view that post
    [–] 32 points 1 year ago* (9 children)

    I didn't know PNG ever went away. I'm using em all the time.

  • source
  • hideshow 9 child comments
  • [–] 17 points 1 year ago* (7 children)

    The title is hyperbole. PNG is lagging behind modern lossless formats in terms of new features.
    This doesn't mean it's a bad format or that it shouldn't be used. In fact, it should still be the default unless you need something it doesn't support or really need to reduce file size.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 9 points 1 year ago (5 children)

    In fact, it should still be the default unless you need something it doesn’t support or really need to reduce file size.

    I disagree. It is wasteful (we're talking ~30% savings with lossless WebP or JPEG-XL) and widely misused, which matters at the massive scale of the Internet with technically inexperienced people making up plenty of those images.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 9 points 1 year ago* (last edited 1 year ago) (4 children)

    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.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 11 points 1 year ago* (3 children)

    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.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 1 year 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.

  • source
  • parent
  • load more comments (1 reply)
  • [–] 12 points 1 year ago* (last edited 1 year ago)

    HDR and EXIF are great changes.. APNG, if already being used for some apps/services, seems a logic choice. Maybe it'll finally mean the end of gifs once and for all?

    What I'm more excited for though, is the improvements in compression that the article hints that are being worked on. Specially if it can beat other more modern formats that have added lossless compression like jpegxl. I feel it's best to have separate formats for lossless and lossy, to prevent the off-chance of lossyness getting through.

  • source
  • [–] 6 points 1 year ago

    Not that I've seen anything wrong with what we currently have, but this is big!

  • source
  • 6 comments in c/technology@lemmy.zip view that post
    [–] 7 points 1 year ago* (5 children)

    Even with the new spec PNG is far behind new standards like AVIF or JPEG XL.

  • source
  • hideshow 5 child comments
  • [–] 4 points 1 year ago (2 children)

    And yet, PNG has more support. If they start supporting the new spec, seems like an improvement to me.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 1 year ago (1 child)

    AVIF is pretty universally supported at this point. JPEG XL just lacks browser support because Google, prefers to push their own .webp and Mozilla is not interested in supporting any non AI focused standards these days.

    Exactly why monopoly power is killer of innovation.

  • source
  • parent
  • hideshow 1 child comment
  • 5 comments in c/webdev@programming.dev view that post
    [–] 5 points 1 year ago

    Now the question is… New PNG vs. JXL. Which is queen?

  • source
  • [–] 4 points 1 year ago (2 children)

    Everyone, go update your 2003 forum avatars.

    My friend, most people weren’t using PNG in 2003, especially for forum avatars. They were glitchy on browsers (IE) for almost a decade after that.

  • source
  • hideshow 2 child comments
  • [–] 4 points 1 year ago* (1 child)

    Even if they did, PNGs are usually a bigger filesize, and forums in 2003 usually had a fairly low filesize limit for avatars.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 1 year ago

    For images with large blocks of solid colors and no gradients, frequently the opposite is true. Screenshots and avatars with solid(transparent) backgrounds are often smaller as png.

    It drives me nuts seeing things like tweets (white and black text) being shared with crazy jpeg artifacting. They'd be so much smaller and so much less ugly as png

  • source
  • parent
  • [–] 3 points 1 year ago

    PNG is back!

    I didn't even know it was gone

  • source