fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-12-25 02:02:11 +00:00
Code Issues Projects Releases Wiki Activity

New note: motivations for dropping JPEG-XL

Browse source
This commit is contained in:
Rohan Kumar 2022-01-12 15:40:35 -08:00
parent 85bde27b93
commit f2774e4ba6
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
1 changed files with 20 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
content/notes/motivations-for-dropping-jpeg-xl.md Normal file
View file

@ -0,0 +1,20 @@
---
title: "Motivations for dropping JPEG-XL"
date: 2023-01-12T15:40:35-08:00
replyURI: "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/"
---
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">}}).