<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><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><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><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>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>0x_rs</author><text>&amp;gt;instead of the entire industry that didn&amp;#x27;t adopt it?&lt;p&gt;Is this a good argument? Nobody is going to adopt something without being natively supported by browsers without ugly js hacks, and when it comes to browser standards it seems to me Google has more leverage than anybody else. Cloudinary has made a lot of posts about JPEG-XL, so you might say they&amp;#x27;re quite biased towards it, but it also seems to me there is some interest in it by multiple companies [0, 1]. I personally very much doubt webp would be &lt;i&gt;anywhere&lt;/i&gt; today without the massive (arguably deceptive) campaigning and double standards it had.&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;&lt;p&gt;1. &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=1178058#c16&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;bugs.chromium.org&amp;#x2F;p&amp;#x2F;chromium&amp;#x2F;issues&amp;#x2F;detail?id=117805...&lt;/a&gt;</text><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><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>