fuif

But they didn't even explain what FUIF or PIK might be in that section or even the entire article! To understand that article required me searching for FUIF [1], PIK [2] and a brief explanation of what JPEG XL is trying to achieve. I double down on my "complaint" - I'd call it constructive criticism - that article was poorly written. It's actually quite a good story that their Free Universal Image Format (FUIF) has achieved what it has. That's a great acronym, especially for a world that thinks JPEG XL is a good acronym! Why not put in in the article. To save anyone else time: [1] https://github.com/cloudinary/fuif [2] https://github.com/google/pik

here is FUIF (one of JXL parents) author writing about benefits of progressive: https://github.com/cloudinary/fuif In short, unlike progressive JPEG, you can serve truncated image files to get lower resolutions

There was also an update to it called FUIF - Free Universal Image Format https://github.com/cloudinary/fuif But it too got superseded by JPEG XL (.jxl) https://jpegxl.info/

yeah. it's partially based on https://github.com/cloudinary/fuif so if you use that part of JPEG XL you'll get something similar out of it.

In terms of getting it into chrome: https://bugs.chromium.org/p/chromium/issues/detail?id=539120 > Keep in mind that the author of the FLIF works on the new FUIF (https://github.com/cloudinary/fuif) which will be part of the JPEG XL. So, probably FLIF will be deprecated soon. And as far as JPEG XL is also based on Google PIX, there is a high probability that Google will support this new format in their Blink engine. https://jpeg.org/jpegxl/index.html

It looks like the the creator (Jon Sneyers) has since (2019) made another image format more focused on the lossy compression, FUIF[0], which itself has been subsumed by the JPEG XL format[1]. I hope the "JPEG" branding doesn't make folks think that JPEG XL isn't also a lossless format! [0] https://github.com/cloudinary/fuif [1] https://jpeg.org/jpegxl/index.html