mirror of
https://git.sr.ht/~seirdy/seirdy.one
synced 2024-12-27 10:52:09 +00:00
24 lines
1.3 KiB
Markdown
24 lines
1.3 KiB
Markdown
---
|
|
title: "Motivations for dropping JPEG-XL"
|
|
date: 2023-01-12T15:40:35-08:00
|
|
date: 2023-01-12T15:51:10-08:00
|
|
replyURI: "https://web.archive.org/web/20230131193442/https://vulpine.club/@eevee/109674417561084417"
|
|
replyTitle: "with the jpeg xl thing…pushing their own formats is convenient for their other products"
|
|
replyType: "SocialMediaPosting"
|
|
replyAuthor: "Eevee"
|
|
replyAuthorURI: "https://eev.ee/"
|
|
syndicatedCopies:
|
|
- title: 'The Fediverse'
|
|
url: 'https://pleroma.envs.net/notice/ARaAr2S33jEXsaYLWy'
|
|
---
|
|
|
|
I do find their decision to drop JPEG-XL from Chromium problematic because it was clearly an example of them ignoring everyone else, showing the limits of Chromium's collaborative decision making. However, "pushing their own formats" wasn't one of their reasons:
|
|
|
|
- Google also dropped plans to make its WebP2 project a real image format at around the same time
|
|
- Google helped define the JPEG-XL spec
|
|
- Google developed the Butteraugli project, which was incorporated into JPEG-XL
|
|
- The reference implementation (libjxl) is mostly a Google project
|
|
|
|
Google is a big part of JPEG-XL, yet Google dropped it along with its own WebP2 a while after seeing AVIF gain widespread support.
|
|
|
|
I previously shared my thoughts on the issue in this post: [Google drops Webp2 and JPEG-XL]({{<relref "/notes/google-drops-jpeg-xl-and-webp2.md">}}).
|