11 ms·

> if you’re the average working web developer it’s been easy to support all of the evergreen browsers for years All the browsers bar Safari. > you’ll see a si

> if you’re the average working web developer it’s been easy to support all of the evergreen browsers for years All the browsers bar Safari. > you’ll see a significant performance or battery life win by dropping Chrome, which the average user will appreciate a lot more than not having WebMIDI or sites nagging them to enable push notifications. I think the average user would much rather have a browser that follows web standards. Why? Because 90% of the apps on the app store could just be websites instead. And what difference does that make? Apple can't take a 30% cut off a website. > I’d be a lot more comfortable allowing Chrome on iOS if it was accompanied by regulatory action banning that and requiring Google to do real QA on other browsers and not use proprietary Chrome APIs on their production sites, which held back Firefox and Safari performance on YouTube for ages because they were using the web components standard instead. This has nothing to do with Chrome, or allowing Chrome on Safari. It has everything to do with the developers at youtube not updating their own service. Any regulations/QA would need to lie with the youtube team, not the chrome team. iOS users shouldn't have to suffer being locked to a historically bad browser because of it.

acdha 4y ago
> All the browsers bar Safari. > I think the average user would much rather have a browser that follows web standards. Which specific unimplemented standards are preventing your work? I’ve opened plenty of bugs in all of the major browsers and it’s decidedly not the case that they’re mostly Safari. Last year’s interoperability push ended with a noticeable lag for Chrome: https://wpt.fyi/interop-2022?stable https://wpt.fyi/interop-2022?stable > This has nothing to do with Chrome, or allowing Chrome on Safari. It has everything to do with the developers at youtube not updating their own service. Yes, we know. Now think about whether it’s possible that working at the same company might make them less quick to prioritize work which undercuts a key selling point their company spent billions marketing. It’s not like the YouTube developers didn’t notice the big effort to put Chrome banners all over the site was a management priority. Anyone who remembers how Microsoft products used to have weird bugs when used in non-IE browsers knows how that could end.
- kouteiheika 4y ago
  > Which specific unimplemented standards are preventing your work? Still no proper Opus support, where it was available in Firefox 10 years ago. Also bugs. My experience is that it's a common occurrence that I make a change, and it works correctly in Firefox and Chrome, but it breaks in Safari and I need a workaround just for it.

acdha 4y ago

> All the browsers bar Safari. > I think the average user would much rather have a browser that follows web standards. Which specific unimplemented standards are preventing your work? I’ve opened plenty of bugs in all of the major browsers and it’s decidedly not the case that they’re mostly Safari. Last year’s interoperability push ended with a noticeable lag for Chrome: https://wpt.fyi/interop-2022?stable https://wpt.fyi/interop-2022?stable > This has nothing to do with Chrome, or allowing Chrome on Safari. It has everything to do with the developers at youtube not updating their own service. Yes, we know. Now think about whether it’s possible that working at the same company might make them less quick to prioritize work which undercuts a key selling point their company spent billions marketing. It’s not like the YouTube developers didn’t notice the big effort to put Chrome banners all over the site was a management priority. Anyone who remembers how Microsoft products used to have weird bugs when used in non-IE browsers knows how that could end.

kouteiheika 4y ago
> Which specific unimplemented standards are preventing your work? Still no proper Opus support, where it was available in Firefox 10 years ago. Also bugs. My experience is that it's a common occurrence that I make a change, and it works correctly in Firefox and Chrome, but it breaks in Safari and I need a workaround just for it.