3 ms·
> Just that it’s not “obviously” impossible. Neither was webm support, but that didn't stop them from taking several years to implement it (and even then it wa
by smoldesu 4y ago
> Just that it’s not “obviously” impossible.
Neither was webm support, but that didn't stop them from taking several years to implement it (and even then it was half-finished). Apple clearly wants to play the superiority game with their own codecs. They have zero incentive to support any codecs they didn't build, and have been known to abandon standards that they help develop.
Nothing is technically impossible for Apple, but codec support is stuck between an ideological/financial rock and a hard place.
- dmitriid 4y ago> Apple clearly wants to play the superiority game with their own codecs. They have zero incentive to support any codecs they didn't build, and have been known to abandon standards that they help develop. And on the other end you have Google who threatens others if they don't bend over and implement Google's codecs in hardware [1]. The codecs space is, and has always been, a game of shitty players. [1] e.g. https://www.protocol.com/bulletins/av1-android-14-requirement https://www.protocol.com/bulletins/av1-android-14-requiremen... and https://www.protocol.com/youtube-tv-roku-issues https://www.protocol.com/youtube-tv-roku-issues
- smoldesu 4y agoAV1 is a more open codec than MOV or AAC, so it's not really any shittier of a play than Apple demanding third-parties use AAC for every iPhone accessory.