4 ms·

Personally, even if Chrome goes ahead with removing support I hope JPEG XL will "win" in the long run by being an attractive "universal" format for all other us

Personally, even if Chrome goes ahead with removing support I hope JPEG XL will "win" in the long run by being an attractive "universal" format for all other use-cases for image compression. So in other words: that it finds an ecosystem elsewhere, slowly takes over outside of the browsers, and then the browsers will adopt it after all. For example, I remember reading somewhere that there are people looking at whether or not it makes sense to convert all of the existing JPEGs to JPEG XL on their servers for storage, then reconstruct the JPEG when needed. If so, then there is a niche where it can find adoption even if browsers don't support it yet. It also looks like it might find a use for medical and scientific imaging. What I personally really would like to know is if it would be possible to losslessly recompress the RAW files from my camera. It looks like it should support everything required, and the claim that it "is the first serious candidate to become a universal image format that “works across the workflow”, in the sense that it is suitable for the lifecycle of a digital image, from capture and authoring to interchange, archival, and delivery" kind of implies that it is, but I haven't seen anyone say it out loud yet. Because I must say: DNG is really slow and clunky to work with, and I bet has terrible compression on top of that.

ksec 4y ago
What if Google demand every Android devices to support AVIF and not JPEG XL? This isn't a fight about whether something is technically superior, it is about marketing, cult and ideology. It wont be long before major force of AOM supporters arrives with new PR points to fight back.
- magicalist 4y ago
  > What if Google demand every Android devices to support AVIF and not JPEG XL? Has there ever been a case when a company has demanded a device not support a codec that wasn't a patent dispute? And what does it mean for a device not to support an image format? Almost all image decoding is done in software. This seems like an unfounded concern.
  - vanderZwan 4y ago
    I wouldn't be surprised if a WASM-based polyfill emerges soon enough
zinekeller 4y ago
> Personally, even if Chrome goes ahead with removing support I hope JPEG XL will "win" in the long run by being an attractive "universal" format for all other use-cases for image compression. So in other words: that it finds an ecosystem elsewhere, slowly takes over outside of the browsers, and then the browsers will adopt it after all. Ah, like how Chrome delayed APNG so much that there was a dedicated extension for it? (https://github.com/davidmz/apng-chrome https://github.com/davidmz/apng-chrome) Sadly the Chrome extension page was removed around June (I assume it's more of cleaning up obsolete extensions rather than something nefarious) but I have recovered its description here: Support for animated PNG images in Google Chrome browser. Chrome 59 now have native support of APNG, so you do not need this extension anymore. Goodbye, it was an interesting 6 years! About APNG format: http://en.wikipedia.org/wiki/APNG http://en.wikipedia.org/wiki/APNG This extension animates IMG elements. Also it animates background images/list style images from css styles (div style="…"), but CSS images support may be incomplete. You can prevent this extension from work on specific domains (Black List mode, default) or allowed it to work ONLY on specific domains (White List mode). Source code is available on GitHub: https://github.com/davidmz/apng-chrome https://github.com/davidmz/apng-chrome WARNING! CAPTCHA may not work on some sites because of this expansion (it is not always possible to correctly detect captcha images). If captcha does not work on some site, just (temporarily) disable the extension on the it. ---------------------------------- Latest notable changes: 3.1.0 (2017-06-07) Chrome 59 now have native support of APNG, so you do not need this extension anymore. Goodbye, it was an interesting 6 years! 3.0.0 (2016-09-12) IT WORKS AGAIN!!! In Chrome 48 (Feb 2016) Google turns off getCSSCanvasContext API. It was the critical part of extension, and within six months the Chrome has no technologies to animate images. Fortunately, it has changed recently and now this extension works again. In version 3 algorithm was changed from canvas animation to APNG → animated WebP conversion. 2.1.4 (2014-11-28) Fixed some incorrect captcha images. 2.1.2 (2014-01-15) Better Reddit support. 2.1.0 (2014-01-12) Partial Reddit emotes support. 2.0.7 (2014-01-12) Redirects support. 2.0.4 (2013-05-26) Ext. was broken because of bug 238071 in Chrome 27. Fixed it. 2.0.3 (2013-03-19) Fixed bug with images with 'auto' height/width in style. 2.0.0 (2012-10-01) Most of the code rewritten. CSS background/list animations is turned off (except inline styles). Fixed slow work in some sites (g+, gmail and so on). 0.7.1 (2012-04-07) animated-gif-captcha images support (strange captchas of wedge.org) 0.7.0 (2011-08-03) fix for facepunch.com (perhaps the only site where this extension is actually used:)) 0.6.9 (2011-07-14) data: url support, fixes for google maps images 0.6.8 (2011-07-09) fixed bug with CAPTCHA images 0.6.7 (2011-07-03) support for list-style-images 0.6.6 (2011-06-30) tracking changes in image's 'src' 0.6.2 (2011-06-30) background-image animation for internal and external CSS

ksec 4y ago

What if Google demand every Android devices to support AVIF and not JPEG XL? This isn't a fight about whether something is technically superior, it is about marketing, cult and ideology. It wont be long before major force of AOM supporters arrives with new PR points to fight back.

magicalist 4y ago
> What if Google demand every Android devices to support AVIF and not JPEG XL? Has there ever been a case when a company has demanded a device not support a codec that wasn't a patent dispute? And what does it mean for a device not to support an image format? Almost all image decoding is done in software. This seems like an unfounded concern.
- vanderZwan 4y ago
  I wouldn't be surprised if a WASM-based polyfill emerges soon enough

zinekeller 4y ago

> Personally, even if Chrome goes ahead with removing support I hope JPEG XL will "win" in the long run by being an attractive "universal" format for all other use-cases for image compression. So in other words: that it finds an ecosystem elsewhere, slowly takes over outside of the browsers, and then the browsers will adopt it after all. Ah, like how Chrome delayed APNG so much that there was a dedicated extension for it? (https://github.com/davidmz/apng-chrome https://github.com/davidmz/apng-chrome) Sadly the Chrome extension page was removed around June (I assume it's more of cleaning up obsolete extensions rather than something nefarious) but I have recovered its description here: Support for animated PNG images in Google Chrome browser. Chrome 59 now have native support of APNG, so you do not need this extension anymore. Goodbye, it was an interesting 6 years! About APNG format: http://en.wikipedia.org/wiki/APNG http://en.wikipedia.org/wiki/APNG This extension animates IMG elements. Also it animates background images/list style images from css styles (div style="…"), but CSS images support may be incomplete. You can prevent this extension from work on specific domains (Black List mode, default) or allowed it to work ONLY on specific domains (White List mode). Source code is available on GitHub: https://github.com/davidmz/apng-chrome https://github.com/davidmz/apng-chrome WARNING! CAPTCHA may not work on some sites because of this expansion (it is not always possible to correctly detect captcha images). If captcha does not work on some site, just (temporarily) disable the extension on the it. ---------------------------------- Latest notable changes: 3.1.0 (2017-06-07) Chrome 59 now have native support of APNG, so you do not need this extension anymore. Goodbye, it was an interesting 6 years! 3.0.0 (2016-09-12) IT WORKS AGAIN!!! In Chrome 48 (Feb 2016) Google turns off getCSSCanvasContext API. It was the critical part of extension, and within six months the Chrome has no technologies to animate images. Fortunately, it has changed recently and now this extension works again. In version 3 algorithm was changed from canvas animation to APNG → animated WebP conversion. 2.1.4 (2014-11-28) Fixed some incorrect captcha images. 2.1.2 (2014-01-15) Better Reddit support. 2.1.0 (2014-01-12) Partial Reddit emotes support. 2.0.7 (2014-01-12) Redirects support. 2.0.4 (2013-05-26) Ext. was broken because of bug 238071 in Chrome 27. Fixed it. 2.0.3 (2013-03-19) Fixed bug with images with 'auto' height/width in style. 2.0.0 (2012-10-01) Most of the code rewritten. CSS background/list animations is turned off (except inline styles). Fixed slow work in some sites (g+, gmail and so on). 0.7.1 (2012-04-07) animated-gif-captcha images support (strange captchas of wedge.org) 0.7.0 (2011-08-03) fix for facepunch.com (perhaps the only site where this extension is actually used:)) 0.6.9 (2011-07-14) data: url support, fixes for google maps images 0.6.8 (2011-07-09) fixed bug with CAPTCHA images 0.6.7 (2011-07-03) support for list-style-images 0.6.6 (2011-06-30) tracking changes in image's 'src' 0.6.2 (2011-06-30) background-image animation for internal and external CSS