zlacker

>>samwil+(OP)
I’m truly scared of Chrome.

It pushes proprietary features, from what I know it starts enforcing some analytics/ads without possibility to block it out and there are other thing too, but since I’m not really an user I don’t track them deeply.

Based on my personal experiences with IE, ActiveX, Adobe Flash and not being able to fill my taxes without Microsoft license (that was around 800$ back then for me not adjusted for inflation) I am afraid the same will happen with Chrome once it gets enough ground.

“Hey, sorry but we can’t sell you toothbrush because you’re using Safari/Firefox/Vivaldi/whatever. Please switch to Chrome and continue with your tracked and dissected purchase route.”

Is there any other anti-Chrome bastion than iOS’ Safari?

Old E2E runner installed Google Chrome on my machine (didn’t even ask but that’s user space on dev machine so whatever) which grew into my MacOS machine. It cannot run in background but there is another daemon that constantly updates it. Multiple times a day I get notification that new service has been installed to run in background.

I’m not sure if that’s something I want to fight for.

>>xlii+5h
If Apple was forced to compete on iOS for the dominant position that Safari holds, it would receive greater investment, add support for vital missing PWA features and potentially as a result grow its desktop market. I believe competition in the long run would break Blinks dominant position, and be better for both consumers and developers.

>>samwil+ei
If Apple was forced to compete

It is not a fair market since the maker of one of the browsers also owns a significant portion of the websites that people use daily. Now Google has to play nice with Safari to some extend, since the don't want to miss out on the lucrative iPhone market. Once Google can offer Chrome on iOS, they will destroy Safari with the same underhanded practices as they did to Firefox (a pattern of subtly breaking Firefox with Google products).

>>microt+Hk
What are these websites ?

Search - I don't really see a browser specific optimization potential here.

YouTube is probably mostly app based on mobile.

Gmail and other gsuite apps are also app based on mobile.

I'd be surprised if they cared about mobile Safari support in those much or if it played a big factor.

>>moonch+yL
All 3 of those sites heavily promoted Chrome to users of other browsers, inaccurately claiming that the service would be better with it (it wasn't).

YouTube also had an interesting example of the problem: they shipped some code using Chrome's early draft of what became Web Components. Firefox and Safari implemented the standard version, but there was a LONG period where YouTube used a very slow polyfill instead of upgrading to the standard version, causing Chrome to appear to be faster because it wasn't all of that extra JavaScript. If YouTube was an independent company they would likely have fixed a poor user experience much faster.