Unclear why Google would straight up reject an open standard. Considering their browser market share, jt feels like they can just kill a standard.
I still have to occasionally convert some images back to jpeg, but the savings from storing all of them in jpeg-xl instead is worth it to me (and avif support is spotty in the same areas, it is only really ahead in browsers and photoshop)
The progressive enhancement feature alone could be quite amazing, and its competitors don’t offer that- No more thumbnail generation! Its competitors can’t offer that! Do they realize how many security holes everyone’s use of “ImageTragick” generates, and how much caching infrastructure is devoted to images?
also, how does he fail to see this as a potential competitive advantage over browser competitors?
Can you expound on this?
No less than 630 vulnerabilities, and almost everyone uses this library, although VIPS is gaining tiny marketshare.
still not great, but this give some context to understanding the number.