←back to thread

A new PNG spec

(www.programmax.net)
625 points bluedel | 2 comments | | HN request time: 0.509s | source
Show context
qwertfisch ◴[] No.44376468[source]
Seems a bit too late? And also, JPEG XL supports all the features and uses already advanced compression (finite-state entropy, like ZStandard). It offers lossy and lossless compression, animated pictures, HDR, EXIF etc.

There is just no need for a PNG update, just adopt JPEG XL.

replies(5): >>44376756 #>>44377176 #>>44378892 #>>44379025 #>>44384951 #
illiac786 ◴[] No.44377176[source]
I really don’t get it. Why, but why? It’s already confusing as hell, why create yet another standard (variant) with no unique selling point?
replies(1): >>44378143 #
pmarreck ◴[] No.44378143[source]
JPEG XL is not a "variant", it is a completely new algorithm that is also fully backwards-compatible with every single JPEG already out there, of which there are probably billions at this point.

It also has pretty much every feature desired in an image standard. It is future-proofed.

You can losslessly re-compress a JPEG into a JPEG-XL file and gain space.

It is a worthy successor (while also being vastly superior to) JPEG.

replies(3): >>44378163 #>>44378359 #>>44378429 #
BobaFloutist ◴[] No.44378359[source]
Is there any risk that if I open a JPEG-XL in something that knows what a JPEG is but not what a JPEG-XL is and then save it, it'll get lossy compressed? Backwards compatibility is awesome, but I know that if I save/upload/share/copy a PNG, it shouldn't change without explicit edits, right?
replies(1): >>44378533 #
illiac786 ◴[] No.44378533[source]
a sw that does not know what jpeg xl is, will not be able to open jxl files. How would it?

Not sure what the previous poster meant with “backward compatible” here. jxl is a different format. It can include every information a jpeg includes, which then maybe qualifies as “backward compatible” but it still is a different format.

replies(2): >>44379111 #>>44379945 #
1. liuliu ◴[] No.44379111[source]
JPEG XL has the mode that in layman's word, allow bit-by-bit round-trip with JPEG.

Original JPEG -> JPEG XL -> Recreated JPEG.

Sha256(Original JPEG) == Sha256(Recreated JPEG).

That's what people meant by "backward compatible".

replies(1): >>44379451 #
2. colejohnson66 ◴[] No.44379451[source]
That’s not “backwards compatible”, but “round tripable” or “lossless reencode”