CPNG, a backwards compatible fork of PNG
richg42.blogspot.com
CPNG, a backwards compatible fork of PNG
1–10 of 122 posts
Re: CPNG, a backwards compatible fork of PNG
#2What a brilliant paragraph. I wish this developer all the success in the world.
Re: CPNG, a backwards compatible fork of PNG
#3Re: CPNG, a backwards compatible fork of PNG
#4Also speaks to either wise or lucky design of PNG itself, that it can support these kinds of backwards-compatible extensions.
Re: CPNG, a backwards compatible fork of PNG
#5Re: CPNG, a backwards compatible fork of PNG
#6Re: CPNG, a backwards compatible fork of PNG
#7For 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
#8How this compares to WebP?
Re: CPNG, a backwards compatible fork of PNG
#9For 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
#10The world needs more work like this. I’m talking about the thoughtful image format but also that applies to the write up too.