fmaury/seirdy.one
1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-09-19 20:02:10 +00:00
Code Issues Projects Releases Wiki Activity
seirdy.one/content/notes/motivations-for-dropping-jpeg-xl.md
Seirdy 35456ecc09
Fix broken links 
Got consent from some more fedi users :3
2024-05-26 02:28:43 -04:00

1.3 KiB
Raw Permalink Blame History

title date date replyURI replyTitle replyType replyAuthor replyAuthorURI syndicatedCopies
Motivations for dropping JPEG-XL 2023-01-12T15:40:35-08:00 2023-01-12T15:51:10-08:00 https://web.archive.org/web/20230131193442/https://vulpine.club/@eevee/109674417561084417 with the jpeg xl thing…pushing their own formats is convenient for their other products SocialMediaPosting Eevee https://eev.ee/
title url
The Fediverse 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">}}).