[joedrago]

I guess it is too soon to say impact-wise one way or another, but I'm the author of libavif (and the avifenc/avifdec tools), which is the reference library for AVIF. I helped it get integrated into Chrome* and I worked with the author of the AVIF layer for Firefox too (it does not use libavif). I've been taking a more advisory/administrative role in the library's development over the last year, but it is basically my brainchild (for better or worse; just the library, not the standard). The folks that have contributed many changes over the last year are some really smart folks and I look forward to seeing where the library goes. I've also put a bunch of work into our HDR rendering pipeline and analysis tools at my current job, which doesn't necessarily have public impact, but mattered/matters a lot to a few teams at work.

* Before anyone asks, I was not involved in any of the recent JPEG-XL removal choices happening over at Google (I don't work there). I was as surprised as everyone else was. I'll admit I haven't given JPEG-XL as much of a R&D spin as I should, but it seems like it has a lot of cool features and if people prefer it to AVIF, game on. I'm proud of the library, but I'd rather people used their preferred format in any avenue and not be locked into something they dislike. I'd certainly rather that any technology succeed or fail on its own merits than any other possible reason.