alt Hacker NewsAlso one which doesn't add new image decoder with built-in VM that is rawdogged in C, like Safari.
Chrome and Firefox are making a very reasonable decision to wait for a memory safe decoder.
Also one which doesn't add new image decoder with built-in VM that is rawdogged in C, like Safari.
Chrome and Firefox are making a very reasonable decision to wait for a memory safe decoder.
Chrome's involvement in the past few years has (until very recently) been anything but reasonable.
That said, have any of them subjected WebP or AVIF to the same strict requirements, or should we reserve those only for less complex codecs actually designed with images in mind?