News for hackers. Stuff that matters.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by Someone1234 on Sunday April 16, 2023 @09:19AM (#35589812)
This is worth looking at:

https://caniuse.com/jpegxl

Unless I'm misunderstanding that, no browser actually ever supported JPEG-XL without a flag (or at all on Safari's cases). No OS appears to have supported it natively either[0]. The reality is that formats have a chicken & 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't adopt it? Feels like there is a bigger issue with JPEG-XL's failure to launch, and they did more than some (Apple? Microsoft?).

[0] https://en.wikipedia.org/wiki/JPEG_XL#Industry_support_and_a...

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by brookst on Sunday April 16, 2023 @09:44AM (#35589976)
Yep. This is like teenagers blaming Walmart for their band's lack of success. "If only they had carried our album and featured it on endcaps!"
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by zinekeller on Sunday April 16, 2023 @10:41AM (#35590418)
Yep, teenagers like Facebook and Adobe - oh wait. Maybe Google is now flexing its anticompetitive muscles now, isn't it?
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by brookst on Sunday April 16, 2023 @11:23AM (#35590747)
I must be failing to understand your comment. The people complaining are FSF, and no matter how hard I squint, I cannot see how fair competition could require Google to be the first one to support a standard that literally nobody else supports.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by zinekeller on Sunday April 16, 2023 @11:37AM (#35590919)
> The people complaining are FSF

Nope, not just FSF. The Chromium team have prototyped JXL, but removed it initially for unknown reasons (https://bugs.chromium.org/p/chromium/issues/detail?id=117805...). Engineering teams including but not limited to Adobe, Facebook, Intel and Shopify have complained about its abrupt removal. Chromium developers have subsequently said that it was "due to low interest" (despite piles of messages from engineering teams both in leading companies and small groups saying otherwise).

> I cannot see how fair competition could require Google to be the first one to support a standard that literally nobody else supports.

First, Adobe products have just included JXL. Second, It's because Google is pushing for AVIF, which was extended from AV1. While it has some advantages (as essentially extended version from AV1), it also has a lot of disaadvantages: https://news.ycombinator.com/item?id=35590516. No one said to remove AVIF in favor of JXL but instead to support JXL regardless of Google's support of AVIF, and some people have seen it as forcing Google-favored AVIF instead of considering all formats developed (like how WebP was rammed a decade ago).

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by SquareWheel on Sunday April 16, 2023 @11:50AM (#35591084)
> but removed it initially for unknown reasons

Just an FYI, they gave their reasons in comment #84 of the thread you linked.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by brigade on Sunday April 16, 2023 @12:27PM (#35591464)
Adobe didn't support WebP until 2021, they're the poster child for not supporting a format until it's popular enough that they need to add support.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by quadrangle on Sunday April 16, 2023 @03:54PM (#35593702)
There's also the more widespread phenomenon of profitable-enough local businesses blaming Walmart for putting them out of business. How do we evaluate which analogy is appropriate?
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by adgjlsfhk1 on Sunday April 16, 2023 @09:45AM (#35589985)
Google has 90% of the market. They are the industry.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by izacus on Sunday April 16, 2023 @09:49AM (#35590008)
So they're now forced to maintain every single format someone invents, keep it compatible and security patched forever? Even though even FOSS champion Mozilla wouldn't touch it?
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by illiarian on Sunday April 16, 2023 @10:13AM (#35590191)
They have no reservations when its their own formats and they force others to implement them on pain of removing essential apps like Youtube.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by izacus on Sunday April 16, 2023 @10:35AM (#35590364)
Big surprise.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jsnell on Sunday April 16, 2023 @11:49AM (#35591065)
JPEG XL is one of their own formats!
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by illiarian on Sunday April 16, 2023 @12:33PM (#35591520)
Then it's internal politics at play. Or perhaps image codecs are not as important to Google.

E.g. Android TV now requires hardware support for AV1 [1] and Google threatened Roku that Rouku would lose Youtube support if it didn't support AV1 in hardware [2]

[1] https://www.protocol.com/bulletins/av1-android-14-requiremen...

[2] https://www.protocol.com/youtube-tv-roku-issues

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by neurostimulant on Sunday April 16, 2023 @02:34PM (#35592912)
What funny is google's own chromecast hardware doesn't support av1, yet they require their competitors to support it.

https://developers.google.com/cast/docs/media

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by ksec on Sunday April 16, 2023 @10:05AM (#35590134)
>So they're now forced to maintain every single format someone invents,

Or they could pick a better format and evaluate it? The question is why the better format here, even though it is the same royalty free ( or patents free in AOM's term ), wasn't picked.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by mynameisvlad on Sunday April 16, 2023 @11:50AM (#35591073)
They could. They could also choose to not to. They could also have done it and their set of reasons doesn’t align with yours.

They’re a private company. They can choose to do whatever they want or don’t want to.

If they don’t want to support JPEGXL, why should they be forced to do it? If it was such a necessary format, it would have been a competitive disadvantage to not have support and that would have forced their hand, but nobody else supports it either so why should Google be forced to if they (clearly) don’t want to.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by ksec on Sunday April 16, 2023 @01:17PM (#35592038)
They dont have to. But they could also not lie about it. Or lie about do no evil ( I know that is no longer their motto ). Or they could also not lie about WebP, AOM or AMP or everything else about being Good.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by mynameisvlad on Sunday April 16, 2023 @01:36PM (#35592295)
I mean they could do all those things, but, once again, they don’t have to. They don’t have a responsibility to anyone but their shareholders and therefore bottom line.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by toyg on Sunday April 16, 2023 @10:06AM (#35590146)
They definitely have a responsibility to shepherd standards that show potential to do good for the internet.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by robin_reala on Sunday April 16, 2023 @11:45AM (#35591024)
They definitely don’t. Globally they don’t even touch 70%, and if you look at specific markets like the US they only just hit 50%.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by adgjlsfhk1 on Sunday April 16, 2023 @12:31PM (#35591501)
this depends a lot on how you count. edge and Samsung Internet are both just reskinned chrome. Safari, Firefox and Opera Hot sound 20%, but that's almost all Safari, and Apple still wants to pretend that their special image format is relevant.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by robin_reala on Sunday April 16, 2023 @01:54PM (#35592477)
Edge isn’t just reskinned Chrome when it comes to image formats: they deliberately don’t support AVIF for example. https://caniuse.com/avif
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by markdog12 on Sunday April 16, 2023 @02:55PM (#35593156)
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by csdreamer7 on Sunday April 16, 2023 @09:57AM (#35590072)
> No OS appears to have supported it natively either[0].

Not sure what you mean by OS. The link you provided shows that Linux with several GNOME and other tools support JPEG-XL (especially GIMP).

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by eviks on Sunday April 16, 2023 @12:15PM (#35591341)
But it's not "native"!
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by 0x_rs on Sunday April 16, 2023 @10:01AM (#35590110)
>instead of the entire industry that didn't adopt it?

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'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 anywhere today without the massive (arguably deceptive) campaigning and double standards it had.

0. https://en.wikipedia.org/wiki/JPEG_XL#Industry_support_and_a...

1. https://bugs.chromium.org/p/chromium/issues/detail?id=117805...

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by SquareWheel on Sunday April 16, 2023 @11:43AM (#35590985)
> Nobody is going to adopt something without being natively supported by browsers without ugly js hacks

That's fair, but it is worth pointing out that <picture> tags support multiple source formats. I serve some logos and other important images as both .png and .webp. Adding additional lines for avif for jxl seem reasonable - especially if browsers are testing new formats.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by mynameisvlad on Sunday April 16, 2023 @11:44AM (#35590995)
Why should Google be the ones solely responsible for pushing forward file formats? Either you criticize everyone for their parts in not adopting it, or not at all. It seems silly to single out Google and Google alone when nobody else batted an eyelash to try and support the format.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by demonshreder on Sunday April 16, 2023 @01:21PM (#35592088)
The majority market share is for Google Chrome, directly and indirectly, thus they are the primary target, while Firefox & Safari will only come next.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jsnell on Sunday April 16, 2023 @11:48AM (#35591050)
Being supported by some browsers is useless. It needs to be supported by all the major browsers, as shown by webp.

Apple did not support JPEG XL, based on past history was unlikely to do so, and despite what you say about Google having the most leverage they have none on Apple. If Apple doesn't want something supported, no iOS browser will support it. And if no iOS browser supports a format, it is not going to be useful in production.

I do find it hilarious that all the people who complained about Chrome supporting webp then went on to complain about Chrome not supporting JPEG XL. They're both Google-created formats not widely supported by the ecosystem!

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by bryanrasmussen on Sunday April 16, 2023 @12:38PM (#35591579)
>And if no iOS browser supports a format, it is not going to be useful in production.

graphics heavy sites often optimize for various platforms instead of serving to just one standard.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by RedShift1 on Sunday April 16, 2023 @12:09PM (#35591283)
JPEG XL is not Google created. The problem here is that there's a conflict of interest, Google has its own image formats and they're being petty about competition.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by zinekeller on Sunday April 16, 2023 @12:25PM (#35591444)
JXL was partly derived from Google technologies although it went to ISO standardisation.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by bryanrasmussen on Sunday April 16, 2023 @12:40PM (#35591600)
Ok so one is controlled by Google and one isn't, the idea that any argument over them was ridiculous seems weird given this salient difference.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by RedShift1 on Sunday April 16, 2023 @01:08PM (#35591899)
Heh that makes it even worse because the people who decided to remove JPEG XL from Chrome claimed it was technically inferior :')
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jsnell on Sunday April 16, 2023 @01:14PM (#35592006)
Of the people listed as the main authors of the JPEG XL spec on Wikipedia, I believe 2 out of 3 worked at Google.

What's the "conflict of interest" you're talking about? AVIF? How is that their own format when JPEG XL isn't?

If Apple, Mozilla and Microsoft wanted JPEG XL and committed to supporting it, I bet Chrome could be convinced to restore the support. But AFAIK those companies have made no such commitment, or even any kind of indication of intent. Why should we have another image format that gets only implemented in Chrome, not the wider web ecosystem? (Of course, they too are members of the foundation building AVIF. Oh my God, so many conflicts of interest!)

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by ksec on Sunday April 16, 2023 @01:24PM (#35592137)
>Of the people listed as the main authors of the JPEG XL spec on Wikipedia, I believe 2 out of 3 worked at Google.

Google Research. Which is similar to Microsoft Research.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jsnell on Sunday April 16, 2023 @01:32PM (#35592234)
I don't know what distinction you're trying to draw there.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by joveian on Monday April 17, 2023 @06:15PM (#35607375)
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by kps on Sunday April 16, 2023 @12:59PM (#35591785)
> I do find it hilarious that all the people who complained about Chrome supporting webp then went on to complain about Chrome not supporting JPEG XL.

They are different formats with different attributes, so it's reasonable to distinguish between them. JPEG XL is a general purpose image format. It's reasonable to want browsers to display it. WebP and AVIF are special-purpose formats, designed to leverage their corresponding video decoders, for delivery of ephemeral images to end-user devices. It's reasonable to object to limited formats that are manifestly crowding out general ones.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by bbarnett on Sunday April 16, 2023 @02:40PM (#35592982)
https://en.wikipedia.org/wiki/JPEG_XL

How is it Google created?

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jsnell on Sunday April 16, 2023 @03:54PM (#35593706)
It was based on Google's submission, the majority of the authors are Google employees, and the majority of the commits to the reference implementation were written by Google employees. You mean other than that?

That's not to say they're the only contributors or should have all the credit. But it does make the "Google is trying to kill an open standard to push their own format" narrative here completely moronic.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by ksec on Sunday April 16, 2023 @10:07AM (#35590151)
>The reality is that formats have a chicken & egg problem.

The same company that gave us WebP. At least Mozilla and Safari did the sane thing and push back against it.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by bastawhiz on Sunday April 16, 2023 @10:39AM (#35590403)
Is your argument that more folks should have pushed back against JPEG XL? Webp was initially released in 2010 when it was the best alternative. JPEG XL came along almost a decade later. The state of image formats is very different.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by zinekeller on Sunday April 16, 2023 @10:44AM (#35590439)
No, instead Google should made WebP a proof-of-concept that there are technological advancements that can improve and made a successor of WebP like they've done with QUIC (to HTTP 3), not force-slinging it to everyone. Also, WebP violates the "two independent implementations" standard - at least AVIF can be argued to have two different implementations (due to dav1d).
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by Spivak on Sunday April 16, 2023 @01:21PM (#35592085)
Huh? Is there some drama because they all support webp so clearly push didn't come to shove.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by kps on Sunday April 16, 2023 @10:35AM (#35590370)
> [0] https://en.wikipedia.org/wiki/JPEG_XL#Industry_support_and_a...

JPEG XL is a general purpose image format, like JPEG and PNG. WebP has one specific purpose: web delivery of ephemeral images, leveraging VP8 hardware decoding driven by consumer consumption devices. Google, and web-oriented companies in general, have no particular interest in general purpose image formats.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by Spivak on Sunday April 16, 2023 @01:13PM (#35591981)
That seems fine then? Browsers are consumer consumption devices. And you have different formats good for other things. That's Apple's philosophy for HEIC.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by webkike on Sunday April 16, 2023 @01:54PM (#35592491)
No they are not. They are information delivery devices being co-opted for content consumption
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by kps on Sunday April 16, 2023 @01:57PM (#35592525)
Although I'm not personally a fan of web apps or Electron, the reality is that browsers are not just consumer consumption devices. And my reading of http://crbug.com/1178058 is that the existence of WebP and AVIF is being used as a justification for removing JPEG XL support.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by GoblinSlayer on Sunday April 16, 2023 @02:16PM (#35592706)
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by GuB-42 on Sunday April 16, 2023 @10:54AM (#35590522)
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.

It is not the case for video. Video is still a huge bandwidth hog, and finding better codecs is worth it, that'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't have that incentive.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by kevin_thibedeau on Sunday April 16, 2023 @02:52PM (#35593129)
Webp max resolution is 16383 x 16383. That is a problem in some applications.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by selcuka on Sunday April 16, 2023 @07:40PM (#35595200)
Why any modern image spec should have a maximum resolution is beyond me.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jonas21 on Sunday April 16, 2023 @10:55PM (#35596373)
WebP is based on VP8, which is a video format. Video formats can have maximum resolutions to make it easier to implement hardware decoders.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by flangola7 on Monday April 17, 2023 @02:08AM (#35597312)
What application? That's 8x 8K or 32x 4K. Even theoretical futuristic giant displays would not need that.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jerryX on Monday April 17, 2023 @03:10AM (#35597627)
Many smartphones now have 200MP e.g. allowing to crop, in astronomy they count in gigapixels ...
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by flangola7 on Tuesday April 18, 2023 @02:17AM (#35610546)
A 200MP smartphone is a nonsensical idea, their lenses are not big enough to utilize that many pixels. Even if it was actually possible, that 200MP is getting auto compressed the moment you message or upload it anywhere. I'm asking about legitimate uses.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by enlyth on Sunday April 16, 2023 @03:13PM (#35593309)
Agreed, PNG and JPEG already serve most purposes.

JPEG = I want to see the content in the image but don't care too much about the quality

PNG = I want a lossless version of this image

Since bandwidth is cheap in most places, the only advantage that JPEG XL has is suddenly not that enticing.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by exmadscientist on Sunday April 16, 2023 @03:32PM (#35593490)
It's not just that. There are purposes that require JPEG and so if I get a WEBP or AVIF or JXL I am actively angry.

I was trying to set the desktop background image on a project laptop last week. I found an image I liked, that would immediately remind me what machine this was when I look at it.

It was an AVIF. Windows 10 won't accept those as desktop backgrounds. It looked, for all intents and purposes, like the search image results were going to give me JPEGs -- the URL ended in .JPG and had "jpeg" as the media type! -- but that is not what I got. This did not work. Refusing to give up, I eventually determined that using curl to retrieve the image gave me a usable JPEG, and so I got my background and now I can tell this stupid project laptop apart.

For my use cases, which is as someone who does light work with images (backgrounds, occasional use in some kind of paint program, occasional insertion into documents or slides), anything that isn't a JPEG or PNG is actively harmful. Not everyone uses images the way I do, but developers need to remember that not everyone is a passive sheep who just stares at things or a power-developer who builds JPEG-XL from source in their sleep. There are people in between, and we don't take kindly to being forgotten.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jemmyw on Sunday April 16, 2023 @06:57PM (#35594967)
We shouldn't use a new format because some website sent you the wrong mime type and you don't know how to use an image converter? By that logic we should still be using .bmp files for all images.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by selcuka on Sunday April 16, 2023 @07:42PM (#35595208)
I believe the main point is that Windows doesn't support AVIF desktop backgrounds, which is annoying. PNG and JPG (and possibly GIF) are common denominators for a vast majority of systems and applications.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by exmadscientist on Sunday April 16, 2023 @07:51PM (#35595244)
The main point is that nothing supports AVIF other than browsers, and one or two image manipulation programs. If I have to open up GIMP every time I want to insert an image into a document, we have lost.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by sroussey on Sunday April 16, 2023 @08:37PM (#35595509)
Every apple device supports AVIF natively and by default.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by olyjohn on Tuesday April 18, 2023 @05:00PM (#35620077)
I guess that's great if you own an Apple device?
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by pasabagi on Monday April 17, 2023 @01:40AM (#35597187)
$ convert yourfile.avif yourfile.jpg
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by exmadscientist on Monday April 17, 2023 @04:05AM (#35597973)
How much time does that waste, every single time I have to interact with these? How much quality does it lose?

Face it, these "modern" image formats are a massive annoyance for everyone except Web engineers.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by pasabagi on Monday April 17, 2023 @04:42AM (#35598198)
... so different formats exist because people want different things out of images, for instance for print, or for web, or for editing, and because all compression algorithms have their own tradeoffs. That's not a web engineer thing.

I can't really imagine a world where you don't have to choose what format files should be in, and I can't really imagine a more easy way to do that conversion.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jemmyw on Monday April 17, 2023 @06:08AM (#35598768)
I don't know that much about the subject but I had an image for a website I was optimising and the avif version was 10x smaller than the png version, even after I'd run through the normal techniques to squeeze it down, and 3x smaller than the jpeg while still looking much better. That's a really significant saving.

Making an image your wallpaper isn't something people do every day, going through an extra step is hardly onerous. And support will increase until it no longer matters.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by afavour on Sunday April 16, 2023 @09:36PM (#35595902)
Certainly it is annoying. But it’s a very poor reason to continue using an inefficient codec.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by eviks on Sunday April 16, 2023 @12:12PM (#35591309)
There are many reasons, just to list a couple:

1) Chrome is much bigger, so it's much more consequential, so it's valid is a bigger target for criticism

2) It's much easier to performantly support the format on some OS without it being "native", so again, lack of browser support is worse, and thus it's valid it's a bigger target for criticism

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by unethical_ban on Sunday April 16, 2023 @12:24PM (#35591423)
You see it's chicken and egg, but then ask why people are upset that the giant chicken with the ability to put out 10,000 eggs a week dropped a feature that was already in their product.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by illiarian on Sunday April 16, 2023 @12:38PM (#35591584)
> https://caniuse.com/jpegxl

This is kinda how standards are supposed to work: at least two independednt implementations [1], released behind a flag to gather developer and user feedback. However it seems that in the end it went nowhere.

[1] See Implementation experience: https://www.w3.org/2021/Process-20211102/#implementation-exp... Among other considerations: "are there independent interoperable implementations of the current specification?"

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by ars on Sunday April 16, 2023 @12:45PM (#35591647)
It's the "behind a flag" part that is the issue.

How are you supposed to get feedback for a feature people can't actually use?

It's like when Debian removed a package I use that was not shipped under the rationale that "no one uses it". Obviously no one uses it - you never actually shipped it, you just had the source available if people wanted to compile it.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by illiarian on Sunday April 16, 2023 @01:18PM (#35592051)
> How are you supposed to get feedback for a feature people can't actually use?

The moment it's out there (that is, not behind a flag), you cannot fix it, update it etc. because people will be relying on the observed behaviour.

The hard part is advertising the feature (at the very least to developers) because there are just too many featurs in modern browsers. Edit: for example, Chrome has Origin Trials https://developer.chrome.com/origintrials/#/trials/active for experimental features.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by ars on Sunday April 16, 2023 @01:45PM (#35592390)
Sure you can - you just do it. You just make the necessary fix.

But you do it quickly, within a short time of launching it. Anyone who was able to make use of it within a couple months, will be able to adapt and fix things.

Once it's been there for a year, then sure, people rely on it. But there's no reason to take so long.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by illiarian on Sunday April 16, 2023 @02:00PM (#35592554)
> Sure you can - you just do it. You just make the necessary fix.

No, you can't. Not simply.

> But you do it quickly, within a short time of launching it. Anyone who was able to make use of it within a couple months, will be able to adapt and fix things.

That's not how the web works. "People who make use of it in a few months" could easily apps and sites serving millions of people. This is a process that applies not only to image codecs, but to, say hardware APIs and interfaces, network protocols etc.

> But there's no reason to take so long.

There are very many reasons from technical to political to anything in between (and sideways, too).

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by ars on Sunday April 16, 2023 @05:01PM (#35594236)
So, if it's behind a flag then people know not to use it, and therefor no one actually uses it. So you can change it if you want, but you never will because you'll never get feedback.

Or, if it's not behind a flag, then you can tell people not to use it, but they will anyway, which is exactly what you want, because then you get feedback. And when you change it, nothing really bad happens.

Sounds like the flag method is a failure, and just releasing it actually works.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by illiarian on Monday April 17, 2023 @01:28AM (#35597136)
All the modern features that you see on the web have gone through the flag method at one point.

In JPEG XL case it failed not because it was behind a flag, and the failure of one feature doesn't mean that the entire system isn't working.

> Sounds like the flag method is a failure, and just releasing it actually works.

No, "just releasing" doesn't work for the reasons I outlined above.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by croes on Sunday April 16, 2023 @12:44PM (#35591637)
It's not really a chicken egg problem.

If a browser doesn't support a format as default nobody will use it unless big players like Apple or Google enforce it.

If Jpeg XL had been enabled some time without a flag they could claim > There is not enough interest from the entire ecosystem to continue experimenting with JPEG XL

but hidden behind a flag there is no way to know.

How many users enable experimental features in their browser?

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by crote on Sunday April 16, 2023 @12:59PM (#35591782)
Yeah, because it is a new format. You don't immediately publicly release support for an experimental format.

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't done until October 2022.

Chrome removed it in December 2022, citing a "lack of interest from the ecosystem", 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'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!

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by pjmlp on Sunday April 16, 2023 @02:22PM (#35592761)
Similar to how they killed WebGL 2.0 compute, actually.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by tourmalinetaco on Monday April 17, 2023 @09:55AM (#35600741)
All while they support WebP, which doesn’t appear to have any support anywhere beyond web browsers.
Re:FSF Slams Google over Dropping JPEG-XL in Chrome by jorvi on Monday April 17, 2023 @12:22PM (#35602977)
> At the time of removal, it had better support than HEIC!

I don't think I've ever encountered a single JPEG-XL image. Meanwhile I've encountered plenty of HEIC and never encountered a problem in dealing with them.

What annoys me more is that despite basically the entire modern tech industry being in support of- and pushing av1, 99% of the most-modern-compression content I encounter is encoded with h265. There's a good reason for it (h265's initial release was about 5 years earlier) but it still annoys me.

I was hoping at least av2 (or whatever it will be called) would be able to get ahead of h266, but I don't see that happening anymore either. Which means were gonna be stuck in the patents quagmire for a long while.

Even worse is that parties outside of AOmedia have created an av1 patent pool, despite the explicit reason for av1 being concocted is to not be patent encumbered. Most nastily, they don't go after AOmedia itself but instead sue small(er) parties using av1 to bully them into paying a license. One would expect AOmedia to bring to bear the full brunt of their collective legal departments to scare off the av1 patent leeches, but, so far, not a peep.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by saltcured on Sunday April 16, 2023 @02:54PM (#35593143)
Does anybody know why the earlier JPEG-XR also never got useful browser support? Are we just going to see this repeating over and over with nice general purpose image formats being relegated to individual vendor-centric ecosystems and never providing widespread interop?

I find it frustrating how computers have gained so much compute and storage capacity but the web seems to be slipping away as ever more consumer-focused and neutered. Having been there since the beginning, I really expected the web tech and browsers to improve and facilitate scientific data sharing. Not being able to natively decode and display any "exotic" imagery without a bunch of server-side nonsense is frustrating.

Today's client machines have so much capability but become totally balkanized when you can't just serve an image tag and display a real scientific image. Instead you either have to hope the users install extra "workstation" tools to display an image after downloading, or deploy absurdly over-engineered "image servers" to do the basic image rendering and ship plain 8-bit JPEGs to the client.

Why can't a browser natively provide some basic range-mapping color transfer function tools for high bit-depth images in an image tag? Why can't it provide a pan-zoom viewing mode for high resolution images in an image tag?

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by Matl on Sunday April 16, 2023 @05:48PM (#35594575)
> why is Google the scapegoat instead of the entire industry that didn't adopt it?

Because on the web Google is 'the industry'. It's not a problem that it was behind a flag, it's a new format after all.

The problem is Google did implement it and then removed support without sufficient explanation. Given their market power and the fact they're behind competing standard, it raises a few questions.

Re:FSF Slams Google over Dropping JPEG-XL in Chrome by IE6 on Monday April 17, 2023 @02:34PM (#35604639)
Anecdotally but sort of related - we've been using google lighthouse and tools like it to try and optimize our site performance and it was always suggested to use "next gen image formats" but we had the same problem where at the time none of the suggested formats really seemed to have good support.