Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I hope Edge and Safari will enable JPEG XL, but not AVIF. AVIF has several disadvantages, for instance, it takes much longer to encode than JPEG XL and it doesn't support progressing decoding.

Google just doesn't like formats created outside their own company. They prefer WebP and AVIF (created by themselves), but dislike JPEG XL (not created by them).



> They prefer WebP and AVIF (created by themselves), but dislike JPEG XL (not created by them).

This is a common misconception; JPEG XL is jointly created by Cloudinary (which employs the author of FLIP/FUIF) and Google Research Zurich (which previously created PIK, and employs authors of Brotli and WebP lossless format as well) with an official blessing by JPEG (which mostly set the goal for the format). The only difference here is that the authors do not belong to the Chrome team.



Safari has already shipped AVIF support with iOS 16 and macOS Ventura.

Apple is a member of AoM backing AV1/AVIF formats, together with other browser vendors.


This may have happened during Steve's era. Who tends to pick the best codec and fight for it.

No under Tim Cook though. They sided with Google already.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: