3 ms·
Also libwebp reached 1.0 only about 8 years after it was added to Chrome. So I don't think this is a major criterion. That said, we are aiming to reach the li
by jonsneyers 4y ago
Also libwebp reached 1.0 only about 8 years after it was added to Chrome. So I don't think this is a major criterion.
That said, we are aiming to reach
the libjxl 1.0 milestone within a reasonable timeframe, i.e. somewhere in 2023, preferably first half.
- chungy 4y agoAnd Mozilla waited for libwebp to reach 1.0 before making the plunge to support it in Firefox. One of the main issues was that libwebp was willing and frequently made backwards-incompatible changes to the codec in the 0.x days; Google simply didn't care about breaking images, but Mozilla cared.
- jonsneyers 4y agoYes, that's a problem when a format is not standardized but controlled by a single entity. JPEG XL is standardized though, and backwards-incompatible changes are essentially impossible.