>Browser vendors have other priorities besides having the latest-greatest compressor: code size, attack surface, long-term maintenance and compatibility risks, and interoperability.

You’ve missed two most important ones: “business reasons”, eg trying to harm some (potential) competitor, and someone trying to get promoted. Don’t assume there are valid technical reasons behind every corporate decision like those; usually there aren’t.

Maybe if JPEG XL had a chat functionality, Google would have a motivation to include it…

But seriously, it's an ISO standard with a free implementation. There's no Google competitor attached to it. Nobody gets prompted for failing to add features. Google is even missing out on a chance to make Safari look outdated again. There's no reason to interpret indifference as a conspiracy.

BTW: I've worked on the HTML5 spec and codecs for many years, so I've seen how the sausage is made on both sides.

Incorrect. Facebook have said they want to use JPEG-XL. Facebook/instagram is definitely a big tech competitor to google, especially in regards to ads.

Daily reminder that Chrome (and Chromium) is not unlike other Google projects: users are its cattle, not its clients. It’s naive to assume good intentions here.

tl;dr USA is evil because it helped Ukraine defend against Russian meddling.

>I doubt that countries bordering Russia are keen to have failed chaotic states with economic problems on their borders.

As opposed to a single, stronger failed state with economic problems?

It's also the only scenario that guarantees long-term stability. Also, it's not like we've hadn't been through this twenty years ago already, and the result was quite good.

How does it guarantee long-term stability?

By eliminating the main perpetrator - Russia. Smaller countries are manageable.

I suppose it might look pointless if you need to jump through the hoops to get it running. In FreeBSD ZFS is properly integrated, and ZFS is a perfectly fine default root filesystem; there's no reason not to use it, except eg very memory-constrained virtual machines.

Note that, thanks to capsicum(4), this vulnerability is not very exploitable.

Thanks, I didn't know about capsicum(4) and I completely overlooked the mention of sandboxing in the impact section.

Being able to get around doesn't matter - what matters is whether it's inconvenient enough to make the propaganda business unprofitable.

And with revision log.