> duplicating largely what AVIF provided That's not a great bar since both of them showed up around the same time. And importantly JXL hits many use cases tha

> duplicating largely what AVIF provided That's not a great bar since both of them showed up around the same time. And importantly JXL hits many use cases that AVIF doesn't. > while being written in an unsafe language They put little emphasis on that part when they were rejecting JXL. If they wanted to call for a safer implementation they could have done that.