Google isn't in control of the hardware Chrome is running on. Many of those devices do support Av1 decode at a hardware level so it is efficient. Apple has complete control over all their hardware, and they don't support av1 decode. They're absolutely holding progress back.
It’s fine to disagree, it’s not unreasonable to have the take that making users pay a cost in terms of extra cpu usage is worth it for the benefits of AV1. But it would be better if you could make that argument without the hostility.
Anyhow, I will also point out that there is plenty of non Apple hardware in use that also doesn’t have dedicated AV1 decoders. I realize that’s changing, but it’s still got to be a low % of devices at the moment with dedicated AV1 support. I think a more user friendly posture from Google would be to only report AV1 capability in WebRTC negotiation or video tag source selection where it can be done energy efficiently. Happy to be shown to be wrong on that, but my understanding is they don’t do that today.
Hostility wasn't my intention. Sorry, it came across that way. Please forgive me. I can see my mistake--I'll try to improve going forward. Thank you for your correction and for keeping a cool head. Last thing I want to do is make the internet a more trollish place. It has plenty of that already.
Google isn't in control of the hardware Chrome is running on. Many of those devices do support Av1 decode at a hardware level so it is efficient. Apple has complete control over all their hardware, and they don't support av1 decode. They're absolutely holding progress back.