>The main ones of note here really are the AV1 support Apple devices -- in fact, most devices -- don't have AV1 hardware support. Meaning playing AV1 content w

>The main ones of note here really are the AV1 support Apple devices -- in fact, most devices -- don't have AV1 hardware support. Meaning playing AV1 content will have a greater impact on battery life or provide a worse experience. That's why Apple doesn't support it. Any reasonable technology stack is going to sniff what the client supports and serve up AV1 to so equipped clients (which hopefully have hardware support), h265, whatever. That falls in the realm of "complete and utter non-issue". Google doesn't care about your experience (this has been shown time and time again). They'll toss whatever corpse of a solution they want over the wall and let it bake in the sun of exposure. Further, notably your comparison includes loads of partials and nones for Firefox as well. Do you also hold that Firefox sucks? Because again, Chrome is Internet Explorer. Google sticks anything and everything in Chrome because it serves Google. >they'd wipe it entirely after a week This is actually a telling comment. At the time vendors discovered that they could circumvent cookie blocking/clearing by just stuffing everything into WebSQL. Again, Google just tossed it over the wall and loads of "bad webdevs" exploited it and went wailing and gnashing that Safari did this or Safari did that, why can't they just circumvent your privacy controls like they could on Chrome.