[unlord]

> Regarding JPEG XL's mobile support, it makes sense it would see limited development if the company that manages one of the biggest mobile players has been the greatest restriction on their success. The lack of support also disincentivises manufacturers to prioritise support.

There was literally no involvement from any hardware vendor in the standardization of JPEG XL. It went from a Call for Proposals in Sept 2018 to Committee Draft in Aug 2019 with very little time for industry feedback. Contrast this with AV1 which had involvement from hardware vendors Intel, NVIDIA, Arm, AMD, Broadcom, Amlogic from the beginning as well as companies who ship media on hardware at scale such as Cisco, Netflix, Samsung and yes Google. These companies reviewed and provided significant feedback on the format that made it suitable for hardware implementation.

https://news.ycombinator.com/threads?id=JyrkiAlakuijala is a lead on the project and a Google employee, and active in JPEG XL development https://github.com/libjxl/libjxl/commits?author=jyrkialakuij...

[OuterVale]

I very much agree with your observation that the involvement from hardware vendors was minimal. It definitely would have been advantageous to slow down, and it's beyond disappointing that it wasn't pursued further. They absolutely dropped the ball in that regard.

AV1, however, is first and foremost a video format. A very popular one at that. It's perfect for video, and that explains the great industry support. The fact it is the most promising option for video is why it's seen hardware vendor support, not because AVIF is ideal. JPEG XL unfortunately doesn't have this luxury, but still could have done better. This doesn't mean that JPEG XL can't see support now, though, and there are plenty of opportunities for hardware support now it's been proven viable.

While there are certainly employees at Google that have contributed to JPEG XL recently, I'm still yet to see any evidence that the company itself has provided any direct support lately.

[Latty]

Isn't that kind of the point though? AV1/AVIF has an extremely strong case for hardware implementations: you need efficient (both in terms of processing and compression) video decoding on modern devices because the battery cost/bandwidth cost is so high otherwise.

Image decoding is nice to have, but less important. When you are deciding to put custom hardware into a device, that's a huge investment in something only useful for that one task. Being compatible with a video format so you can share that hardware between the two tasks is a huge win for hardware manufacturers who get two-for-one, and for the rate of adoption.

With AV1 already very efficient and rolled out in a lot of hardware already, it just has a huge advantage.

[paulddraper]

> it makes sense it would see limited development if the company that manages one of the biggest mobile players has been the greatest restriction on their success

Huh? Isn't Apple pro-JPEG XL?

[OuterVale]

I was referring to Google with Android. You're correct in thinking Apple is pro JPEG XL.