Chrome is developed by Google, but I assume you know that. I don’t understand why this childish post gets two points.

However, Google does support JPEG XL, they are still working on the library (which is why they released the CVE), and I think they are still major contributors and it is largely based on their work (2 of the 3 main authors of the spec are Google employees, the 3rd Works for Cloudinary). It was specifically the Chrome team that decided to remove JPEG XL; This is not final, they have already indicated that they want to bring it back if it would be helpful.

This is what I mean: Chrome makes its own decisions, and this wasn’t a decision that came from the top because Google was going to pull everyone off JPEG XL as well. But they are still very active.

i know that. This is exactly the problem! Many companies had just completed support for JPEG XL or were developing it, but things went wrong because Google pulled the plug without warning.

Hello. There are companies that have indicated their desire to support the file format, but are waiting for browser support. But most of these companies did not do so, because of the latter; They hardly need development, all they have to do is integrate libjxl, which is not really a problem. They don’t have to implement specifications.

exactly. It is a chicken and egg problem that must be smoothed out. This is impossible as long as the monopolist refuses to support it. That’s the point.

If you want to be really objective, you should mainly point to Mozilla and Apple, not Google. Mozilla because of the feature tag that’s been around for two and a half years but hasn’t caught on yet, and Apple because it’s too slow. And probably also Microsoft, because they and Apple don’t support it in their OS either. But Apple in particular is the big problem here, due to the large market share of Safari iOS. Safari macOS isn’t that exciting, but unfortunately that’s where the iOS version goes. We should be happy that they put it in the browser and not in the OS, as they did with APNG, support on macOS will still take years as there are still many Intel Macs around. Another example is where it was Apple that initially rejected this file format, until they had a use case for it themselves.

I’ve been a web developer for over 20 years and have seen a lot of similar things. It’s very rare for the Chrome team to be the ones working against something like this; In fact, they are often the first or even the main supporters. You can call my response childish, but check your data first.

[Reactie gewijzigd door Werelds op 27 september 2023 16:24]