Hacker News new | ask | show | jobs
by brucethemoose2 872 days ago
When the Google JXL controversy first went down, I found that Google's commit rejecting JXL was authored by someone with AOMedia contributions, and that the manager who signed off and commented on it had some interview about the benefits of AV1.

The links are buried somewhere on Phoronix, I am looking... But what I am saying is Google's rejection of JXL seems to be as bad as it looks.
3 comments
SahAssar 872 days ago
Given google and chromes involvement with AOMedia I think that its pretty natural that anyone focused on image/video codecs in chrome would have some sort of (distant or direct) connection to AOMedia.

If AOMedia was profit driven in any way (like MPEGLA sorta is via patent pools) it'd look worse, but in this case I just think it's the case that the pool of people working on codec support in a particular browser probably isn't that large so the overlap is to be expected.

link
cjawdb 872 days ago
The commit to add the flag saying JXL was being removed soon was reviewed and approved by James Zern, who also created and authored the commit that actually ripped out the JXL code from Chromium. Zern is one of the co-authors of WebP and is the primary contributor to libwebp.
link
brucethemoose2 872 days ago
Hmm, wasn't the name I remembered.

I hate to claim something without a citation, but for the life of me I can't find my Phoronix comment... Only my other comments referencing it.

link
fngjdflmdflg 872 days ago
I see this comment here[0] from one of the developers of av1/avif[1] but it is important to note that nowhere is it mentioned that it is him who made the decision to reject jxl.

[0] https://groups.google.com/a/chromium.org/g/blink-dev/c/WjCKc...

[1] https://research.google/people/james-bankoski/

link