It is Apple throwing up objections to focusing on other things as far as interop goes though. They have alot of weight in the discussion at hand.
I know Google throws some up too (JPEG XL much) but Apple is somewhat notorious for this.
I should also mention, there was an episode of the ShopTalk Show podcast where their developer evangelist was pushing for most of the things in this list when talking about Interop, which makes me believe they had their minds pretty well decided going into the whole thing.
Whenever I see people complain about this, it always seems to be specs. that aren’t on the standards track. Which basically means that it’s a spec. that Google wrote and both Mozilla and Apple rejected.
It takes only two independent implementations to make something a standard. If it’s not on the standards track, it means Google couldn’t convince anybody else to implement it.
This is not Apple throwing up objections. This is Google trying to push bad stuff unilaterally and nobody else going along with it.
no_wizard|2 years ago
I know Google throws some up too (JPEG XL much) but Apple is somewhat notorious for this.
I should also mention, there was an episode of the ShopTalk Show podcast where their developer evangelist was pushing for most of the things in this list when talking about Interop, which makes me believe they had their minds pretty well decided going into the whole thing.
JimDabell|2 years ago
It takes only two independent implementations to make something a standard. If it’s not on the standards track, it means Google couldn’t convince anybody else to implement it.
This is not Apple throwing up objections. This is Google trying to push bad stuff unilaterally and nobody else going along with it.