Hacker News new | ask | show | jobs
by fc417fc802 8 days ago
You say that as though Google isn't notorious for killing their own successful and well received products for seemingly no reason.

It's incontrovertible that Google did attempt to kill browser adoption of jxl at one point. Thankfully they seem to have reversed course.

1 comments

They only reversed under pressure from the Safari and Firefox folks.

The killing of JXL did push the ever-talented Jyrki to create jpegli, which was honestly a wonder.

Thank you.

Jpegli is still a hidden gem. People don't yet understand how great it is.

Mozilla's position from when Chrome first dropped it to September 2024 was "the benefits it provides are not significant enough on their own to justify the cost of adding another raster image format to the Web" [0], which they say is a "neutral" stance. Then like Chrome they only agreed to try it with jxl-rs [1], which is still their present stance. They are a complete passenger in this whole affair, like all other standards, where they basically just copy one side or the other (usually the more conservative side).

It's really bizarre to me that this is presented as "killing the standard". Is Apple also killing mechanical keyboards and hobby electronics development because they're the only ones who don't support Web USB or Web Serial? I strongly prefer having JXL and Web USB/Serial in my browser (FF for the last 20 years), but come on. If we don't like how much power browsers have in software distribution, then maybe software distribution outside of browsers should get fixed.

* [0] https://github.com/mozilla/standards-positions/issues/522

* [1] https://github.com/mozilla/standards-positions/pull/1064

> Is Apple also killing mechanical keyboards and hobby electronics development

Obviously not, but they are killing as web standards the things they omit. At present for something to be standard it needs support from safari and chrome. That's just the current state of the world.

If tomorrow safari removed support for png that would effectively kill it as a web standard (assuming it didn't lead to mass revolt ofc).

Firefox isn't even enabling it
They are working on it. It is in Firefox Nightly behind a flag.