<story><title>FSF Slams Google over Dropping JPEG-XL in Chrome</title><url>https://www.phoronix.com/news/FSF-Slams-Google-JPEG-XL</url></story><parent_chain><item><author>Someone1234</author><text>This is worth looking at:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;caniuse.com&amp;#x2F;jpegxl&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;caniuse.com&amp;#x2F;jpegxl&lt;/a&gt;&lt;p&gt;Unless I&amp;#x27;m misunderstanding that, no browser actually ever supported JPEG-XL without a flag (or at all on Safari&amp;#x27;s cases). No OS appears to have supported it natively either[0]. The reality is that formats have a chicken &amp;amp; egg problem. Normally Google deserves to get dunked on, but in this case, why is Google the scapegoat instead of the entire industry that didn&amp;#x27;t adopt it? Feels like there is a bigger issue with JPEG-XL&amp;#x27;s failure to launch, and they did more than some (Apple? Microsoft?).&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;JPEG_XL#Industry_support_and_adoption&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;JPEG_XL#Industry_support_and_a...&lt;/a&gt;</text></item></parent_chain><comment><author>crote</author><text>Yeah, because it is a new format. You don&amp;#x27;t immediately publicly release support for an experimental format.&lt;p&gt;Chrome added support for the in-progress version of JPEG XL in April 2021. The core coding specification was finished in March 2022, and the last part of the spec wasn&amp;#x27;t done until October 2022.&lt;p&gt;Chrome removed it in December 2022, citing a &amp;quot;lack of interest from the ecosystem&amp;quot;, despite it having support in most major image editors already. It was a new format which was rapidly being adopted and a lot of major players were very excited about it, but Chrome&amp;#x27;s removal pretty much killed it due to their dominance in the browser space. At the time of removal, it had better support than HEIC!</text></comment>
<story><title>FSF Slams Google over Dropping JPEG-XL in Chrome</title><url>https://www.phoronix.com/news/FSF-Slams-Google-JPEG-XL</url></story><parent_chain><item><author>Someone1234</author><text>This is worth looking at:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;caniuse.com&amp;#x2F;jpegxl&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;caniuse.com&amp;#x2F;jpegxl&lt;/a&gt;&lt;p&gt;Unless I&amp;#x27;m misunderstanding that, no browser actually ever supported JPEG-XL without a flag (or at all on Safari&amp;#x27;s cases). No OS appears to have supported it natively either[0]. The reality is that formats have a chicken &amp;amp; egg problem. Normally Google deserves to get dunked on, but in this case, why is Google the scapegoat instead of the entire industry that didn&amp;#x27;t adopt it? Feels like there is a bigger issue with JPEG-XL&amp;#x27;s failure to launch, and they did more than some (Apple? Microsoft?).&lt;p&gt;[0] &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;JPEG_XL#Industry_support_and_adoption&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;en.wikipedia.org&amp;#x2F;wiki&amp;#x2F;JPEG_XL#Industry_support_and_a...&lt;/a&gt;</text></item></parent_chain><comment><author>GuB-42</author><text>The problem is that old PNG and JPEG are good enough for most purposes. They are certainly not as efficient but with todays technology and bandwidth, there is little downside to using JPEG and you know it will be supported everywhere.&lt;p&gt;It is not the case for video. Video is still a huge bandwidth hog, and finding better codecs is worth it, that&amp;#x27;s why they get better support. Webp is a clever hack as it is essentially a single frame webm video, so if you have webm support, which is worth it, then you can have webp almost for free, JPEG-XL doesn&amp;#x27;t have that incentive.</text></comment>