TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

FSF Slams Google over Dropping JPEG-XL in Chrome

228 点作者 YakBizzarro大约 2 年前

16 条评论

Someone1234大约 2 年前
This is worth looking at:<p><a href="https:&#x2F;&#x2F;caniuse.com&#x2F;jpegxl" rel="nofollow">https:&#x2F;&#x2F;caniuse.com&#x2F;jpegxl</a><p>Unless I&#x27;m misunderstanding that, no browser actually ever supported JPEG-XL without a flag (or at all on Safari&#x27;s cases). No OS appears to have supported it natively either[0]. The reality is that formats have a chicken &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&#x27;t adopt it? Feels like there is a bigger issue with JPEG-XL&#x27;s failure to launch, and they did more than some (Apple? Microsoft?).<p>[0] <a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;JPEG_XL#Industry_support_and_adoption" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;JPEG_XL#Industry_support_and_a...</a>
评论 #35591782 未加载
评论 #35590110 未加载
评论 #35590522 未加载
评论 #35590370 未加载
评论 #35590072 未加载
评论 #35593143 未加载
评论 #35594575 未加载
评论 #35591309 未加载
评论 #35589985 未加载
评论 #35590151 未加载
评论 #35591637 未加载
评论 #35604639 未加载
评论 #35591423 未加载
评论 #35591584 未加载
评论 #35589976 未加载
samwillis大约 2 年前
&gt; <i>While we can&#x27;t link to Google&#x27;s issue tracker directly because of another freedom issue -- its use of nonfree JavaScript -- we&#x27;re told ...</i><p>While there may be genuinely good arguments for keeping JPEG-XL, I cannot take seriously the arguments of an organisation that cuts itself off from the rest of the world for such silly reasons.<p>Edit: Google&#x27;s argument that there wasn&#x27;t enough interest is equally impossible to take seriously when it was always behind an optional flag. No web devs are going to invest time in developing JPEG-XL functionality until their users can actually use it.
评论 #35590314 未加载
评论 #35590451 未加载
评论 #35591665 未加载
评论 #35589792 未加载
评论 #35590740 未加载
评论 #35589978 未加载
评论 #35589601 未加载
xoa大约 2 年前
So a few dozen comments, but so far it doesn&#x27;t look like any mention the immediate thing that jumped out at me which was the claims vs AVIF:<p>&gt;<i>&quot;In turn, what users will be given is yet another facet of the web that Google itself controls: the AVIF format.&quot;</i><p>Huh? I&#x27;ll admit I haven&#x27;t been following codecs as super ultra closely as I used to, but I thought AOM was a pretty broad coalition of varying interests and AV1 an open, royalty free codec that was plenty open source friendly? I&#x27;ve heard plenty of reasonable arguments that JPEG XL has some real technical advantages over AVIF and as well as superior performance is much more feature rich and scalable. So I could see people being bummed for that. But this is the first time I&#x27;ve heard the assertion that it&#x27;s somehow a Google project? I mean, AOM&#x27;s libavif reference is BSD too [0]? I&#x27;d love some more details on that from anyone who has been following this more closely. I can even understand if AOM isn&#x27;t as community friendly and an accusation that it&#x27;s dominated by big corps, but in that case why single out Google alone? From wiki:<p>&gt;<i>The governing members of the Alliance for Open Media are Amazon, Apple, ARM, Cisco, Facebook, Google, Huawei, Intel, Microsoft, Mozilla, Netflix, Nvidia, Samsung Electronics and Tencent.</i><p>Like, Google is certainly significant, but that&#x27;s a lot of equally heavy hitters. And interesting that Mozilla is there too.<p>----<p>0: <a href="https:&#x2F;&#x2F;github.com&#x2F;AOMediaCodec&#x2F;libavif">https:&#x2F;&#x2F;github.com&#x2F;AOMediaCodec&#x2F;libavif</a>
评论 #35590612 未加载
评论 #35590506 未加载
评论 #35590435 未加载
csdreamer7大约 2 年前
One of the most interesting things to me is that JPEG-XL is under an open Patent License, unlike the original JPEG.<p><a href="https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;JPEG_XL" rel="nofollow">https:&#x2F;&#x2F;en.wikipedia.org&#x2F;wiki&#x2F;JPEG_XL</a><p>Also, Google contributed quite a bit to it&#x27;s development. As the patent grants show:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;ImageMagick&#x2F;jpeg-xl&#x2F;blob&#x2F;main&#x2F;PATENTS">https:&#x2F;&#x2F;github.com&#x2F;ImageMagick&#x2F;jpeg-xl&#x2F;blob&#x2F;main&#x2F;PATENTS</a><p><a href="https:&#x2F;&#x2F;github.com&#x2F;libjxl&#x2F;libjxl&#x2F;blob&#x2F;main&#x2F;PATENTS">https:&#x2F;&#x2F;github.com&#x2F;libjxl&#x2F;libjxl&#x2F;blob&#x2F;main&#x2F;PATENTS</a><p>Microsoft seemed to have gotten a patent on part of it&#x27;s implementation (which Google also tried to get). Not sure if Google will pay to invalidate that patent, but I have a feeling they are more likely to defend AVIF.<p><a href="https:&#x2F;&#x2F;www.theregister.com&#x2F;2022&#x2F;02&#x2F;17&#x2F;microsoft_ans_patent&#x2F;" rel="nofollow">https:&#x2F;&#x2F;www.theregister.com&#x2F;2022&#x2F;02&#x2F;17&#x2F;microsoft_ans_patent&#x2F;</a><p>Google&#x27;s control is a little concerning, but I do feel there are bigger fish to fry then choosing between two free formats. A bigger concern is the H.264 and H.265 patents domination of video.
评论 #35590243 未加载
Y_Y大约 2 年前
While I&#x27;m aligned with the FSF in most things, I&#x27;m happy to link to a bug tracker despite its shitty JS.<p><a href="https:&#x2F;&#x2F;chromium-review.googlesource.com&#x2F;c&#x2F;chromium&#x2F;src&#x2F;+&#x2F;4081749" rel="nofollow">https:&#x2F;&#x2F;chromium-review.googlesource.com&#x2F;c&#x2F;chromium&#x2F;src&#x2F;+&#x2F;40...</a><p>Maybe they&#x27;re sour about webp not obseleting all other formats by now?
评论 #35589807 未加载
zxcvbn4038大约 2 年前
Mozilla had the same issue - it was one engineer who stubbornly kept webp support out of the browser for years. Then he quit or got laid off and Mozilla finally got support. Mozilla also refused to support Yubikey for years, which we are still paying for now. It seems to me like Mozilla forgot really quickly what life was like when Internet Explorer was the dominant browser. Half the reason Chrome can ignore community outrage is because Mozilla decided existing options were &quot;good enough&quot; and stopped being competition.<p>That said though, that FSF guy is nuts. He can&#x27;t link to their bug tracker because it uses Javascript? I think that battle is lost. But he did obviously read the tracker, does this mean he has to remove his tinfoil hat and go bathe in the living waters of Richard Stallman&#x27;s bathtub?
评论 #35593643 未加载
zamadatix大约 2 年前
Discussion about the root article from FSF:<p>- <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35554107" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35554107</a><p>Similar discussions when Chrome&#x2F;Mozilla were removing it:<p>- <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=33563378" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=33563378</a> (dang&#x27;s comment has a list of additional related at the time)<p>- <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=33803941" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=33803941</a><p>Relevant discussions:<p>- <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35212522" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35212522</a><p>- <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=33442281" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=33442281</a><p>- <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35018672" rel="nofollow">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=35018672</a>
teddyh大约 2 年前
Actual link: <a href="https:&#x2F;&#x2F;www.fsf.org&#x2F;blogs&#x2F;community&#x2F;googles-decision-to-deprecate-jpeg-xl-emphasizes-the-need-for-browser-choice-and-free-formats" rel="nofollow">https:&#x2F;&#x2F;www.fsf.org&#x2F;blogs&#x2F;community&#x2F;googles-decision-to-depr...</a>
threeseed大约 2 年前
To save people some clicks here are the two discussions:<p>* <a href="https:&#x2F;&#x2F;groups.google.com&#x2F;a&#x2F;chromium.org&#x2F;g&#x2F;blink-dev&#x2F;c&#x2F;WjCKcBw219k&#x2F;m&#x2F;xX-NnWtTBQAJ" rel="nofollow">https:&#x2F;&#x2F;groups.google.com&#x2F;a&#x2F;chromium.org&#x2F;g&#x2F;blink-dev&#x2F;c&#x2F;WjCKc...</a><p>* <a href="https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=1178058#c183" rel="nofollow">https:&#x2F;&#x2F;bugs.chromium.org&#x2F;p&#x2F;chromium&#x2F;issues&#x2F;detail?id=117805...</a>
CharlesW大约 2 年前
All of the people here who are so passionate about JPEG-XL will be happy to learn that there&#x27;s nothing preventing them from using it on their sites right now:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;niutech&#x2F;jxl.js">https:&#x2F;&#x2F;github.com&#x2F;niutech&#x2F;jxl.js</a><p>If you want Chrome to ship with JPEG-XL support, use it. At some point, browser makers will decide it&#x27;s worth the incremental cost (to them and all users) to add it.
评论 #35593791 未加载
jeroenhd大约 2 年前
Google removes a standard nobody uses, I don&#x27;t see the problem. AVIF is a decent alternative that can actually be used in modern browsers, with WebP as a fallback.<p>We&#x27;ve got plenty of open image formats for the web already. I don&#x27;t get why people get so hung up about JPEG XL, it&#x27;s not as if they&#x27;re trying to force HEIF onto you like some other tech companies do.
评论 #35590708 未加载
评论 #35594452 未加载
devinprater大约 2 年前
FSF slams Google? Do they even have enough power to slap companies on the wrist anymore?
评论 #35590494 未加载
iambateman大约 2 年前
I mean…it’s a PR issue more than anything. I know what webp is and I had never heard of jpeg-xl.<p>I think that’s true for a lot of people. Maybe one of them is better, but webp definitely has a distribution advantage by a mile.
ifeeltriedboss大约 2 年前
Google is so SLAMMED now
评论 #35590502 未加载
评论 #35600684 未加载
bunbun69大约 2 年前
I thought HackerNews and Reddit hated words such as “slams” in the title. Guess it’s okay now because we love FSF and Phoronix
评论 #35601356 未加载
Jyaif大约 2 年前
In this case, Google should be applauded for not pushing down everyone&#x27;s throat a new image format <i>they</i> created.
评论 #35590177 未加载