Nobody is stopping you from using jpegxl.

This is a vacuous statement. No one is stopping me from using JPEG XL in the same sense that no one is stopping me from using DIMG10K, a format I just invented. But if I attempt to use either of these in my website today, Chrome will not render them.

In a very real sense Google is currently stopping web authors from using JPEG XL.

▲

jeffbee 7 hours ago | parent [-]

The web was designed from the start to solve this problem and you can serve alternate formats to user agents which will select the one they support.

▲

dpark 7 hours ago | parent [-]

Your statement here amounts to “you can serve JPEG XL to other browsers, just not Chrome”.

Yeah, that’s what I said.

▲

jeffbee 6 hours ago | parent [-]

This is the way of web. Sites don't get to dictate what the user agent does. The clue is in the name: user agent.

	▲	dpark 6 hours ago \| parent [-]
		Okay. So putting it together… If the user agent does not support JPEG XL, then you cannot use it. “Nobody is stopping you from using jpegxl” except Google.

▲

xg15 8 hours ago | parent | prev [-]

Then what is this article about?

	▲	jeffbee 8 hours ago \| parent [-]
		It's a meta-commentary about the death of critical thinking and the ease with which mindless mobs can be whipped. From the jump, the article commits a logical error, suggesting that Google killed jpegxl because it favors avif, which is "homegrown". jpegxl, of course, was also written by Google, so this sentence isn't even internally consistent.