Jon Sneyers

There have been some optimizations, but only to the decode part, not the encode part. Notice that x264 "lossless" is most likely not lossless, because it works in a lossy...

You can already try e.g. `flif -E10` if you want faster/worse compression now. The reduced maniac properties thing is an orthogonal speedup idea, but experiments/implementation of that still has to...

Reduced maniac properties is an optimization that can be done within the current bitstream (just need to encode to a restricted subset of the format, and detect this at decode...

These type of images with text with subpixel rendering does indeed tend to compress better with PNG and WebP, which use an interlaced (RGBRGBRGB....) representation, than with JPEG XL, which...

It looks like this is caused by the signaling cost of the MA trees themselves not being properly taken into account.

The _name_ of a media type is not necessarily the same thing as the commonly used filename extension associated with that media type. For example, there's the name "jpeg" (image/jpeg),...

What percentage of the other IANA media types in this list are actually supported by any browser? I am not aware of any browser supporting, say, Microsoft Word documents or...

I think that whenever we produce integer output buffers in the API (i.e. uint8 or uint16), we should do some dithering when quantizing our internal floats to integers. Applications will...

Just decoding to 16-bit and doing a dithered quantization to 8-bit also works. The information is already available in the jxl, it's just that it gets thrown away at the...

There is no synchronization in the codestream, but assuming the headers are OK and the errors are bitflips, not insertions or deletions, you could try to decode all groups and...