Comment by quikoa

Comment by quikoa 6 hours ago

10 replies

View on Hacker News

Didn't Google refuse adding JpegXL because they claimed there wasn't enough interest? I don't think they refused out of security concerns but maybe I'm misremembering that.

pixelesque 6 hours ago

Google argued that duplicating largely (I know JpegXL does support a bit more, but from most users' perspectives, they're largely right) what AVIF provided while being written in an unsafe language was not what they wanted in terms in increasing the attack surface.

Reply View 6 replies
  • adzm 5 hours ago

    And it really was the right move at the time, imo. JXL however now has better implementations and better momentum in the wider ecosystem and not just yet another image format that gets put into chrome and de facto becomes a standard.

    Reply View 5 replies
gcr 3 hours ago

Google refused to merge JpegXL as a strategy play to promote AVIF, which was in use by other teams (i think Photos?). Internally, chrome engineers were supportive of jxl but were overridden by leadership.

Reply View 2 replies
  • zaphar 2 hours ago

    Do you have actual sources for this? Because the other people commenting about how the newer library removes most of the concerns explains this better than an unsubstantiated speculation about promoting AVIF.

    Reply View 1 reply
    • themerone an hour ago

      If you look at the issue tracker, the creator of Webp killed it because of untrue claims there was no interest or advantages over existing formats.

      Concerns about the implementation only came up after years of pushback forced google ton reconsider.

      Reply View 0 replies