On Fri, Nov 11, 2022 at 4:58 PM 'Jim Bankoski' via blink-dev < blink-dev@chromium.org> wrote:
> Helping the web to evolve is challenging, and it requires us to make > difficult choices. We've also heard from our browser and device partners > that every additional format adds costs (monetary or hardware), and we’re > very much aware that these costs are borne by those outside of Google. When > we evaluate new media formats, the first question we have to ask is whether > the format works best for the web. With respect to new image formats such > as JPEG XL, that means we have to look comprehensively at many factors: > compression performance across a broad range of images; is the decoder > fast, allowing for speedy rendering of smaller images; are there fast > encoders, ideally with hardware support, that keep encoding costs > reasonable for large users; can we optimize existing formats to meet any > new use-cases, rather than adding support for an additional format; do > other browsers and OSes support it? > > After weighing the data, we’ve decided to stop Chrome’s JPEG XL > experiment and remove the code associated with the experiment. We'll work > to publish data in the next couple of weeks. > > For those who want to use JPEG XL in Chrome, we believe a WebAssembly > (Wasm) implementation is both performant and a great path forward. > JPEG XL Wasm: https://github.com/GoogleChromeLabs/squoosh/tree/dev/codecs/jxl -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CALgRrLn%3D%3DNnfJOLKzXwDDxyh8m%3D5-PqDneoN8Wcug4SjKEO30Q%40mail.gmail.com.
