Live data from Hacker News

CPNG, a backwards compatible fork of PNG

richg42.blogspot.com

1–10 of 122 posts

Re: CPNG, a backwards compatible fork of PNG

#2
> Why continue messing with PNG at all? Because if you can figure out how to squeeze new features into PNG in a backwards compatible way, it's instantly compatible with all browsers, OS's, engines, etc. This is valuable

What a brilliant paragraph. I wish this developer all the success in the world.

Re: CPNG, a backwards compatible fork of PNG

#5
That's really cool! I stumbled across libpng being 10+x slower to encode than jpg and tiff at work. The LOGLUV32 part is very clever. I particularly like the tonemapped fallback and general idea to build on top instead of reinventing. That said I hope these format extensions don't end up in compatibility hell, where viewing the full info image is hit or miss between different CPNG decoders.

Re: CPNG, a backwards compatible fork of PNG

#7
This sounds pretty amazing.

For CPNG-aware libraries, the performance improvements sound impressive.

For old (CPNG-unaware) libraries: should I expect any performance drop reading a CPNG image compared to if the image had remained PNG? Similarly, how much larger will a CPNG be than a PNG?

Re: CPNG, a backwards compatible fork of PNG

#9
What is the modern power ranking on image formats?

For lossless, what is typically the most efficient size wise? Decompression speed?

For lossy?

I am not in a situation where these micro-optimizations mean much to me, and always default to png, but curious to know where the state of the art is today.

Re: CPNG, a backwards compatible fork of PNG

#10
I loved reading this even though I personally have zero need myself. I enjoyed the rationale and he engineering.

The world needs more work like this. I’m talking about the thoughtful image format but also that applies to the write up too.

Post reply on HN