3 ms·
Unless Meet and other Google apps are really tailored to subperform under firefox I don't think it's a solid case. If google devs code doesn't run as fast in f
by agumonkey 5y ago
Unless Meet and other Google apps are really tailored to subperform under firefox I don't think it's a solid case.
If google devs code doesn't run as fast in firefox why should google take the blame ?
or maybe google is using non html5 apis to tap into chrome for faster perf in which case things are muddy.. since whatwg kinda allows unofficial apis
- read_if_gay_ 5y agoObviously, a private company can do what they want and they shouldn't be forced to make their code run on other platforms.
- dathinab 5y agoNo, IMHO they should be forced to comply with web standard and at least try to work with browsers they don't support first class. (Microsoft simply doesn't allow you to open any of their web apps, weather it's for teams or some of their other apps.) Especially if it involves quasi monopolies. I.e. the it's a quasi Monopoly of chrome like browsers spear headed by Google and Microsoft.
- read_if_gay_ 5y agoI agree, I should've made clearer I was being sarcastic. The quasi-monopoly thing is often ignored when it comes to Big Tech silencing voices.
- dmitriid 5y ago> No, IMHO they should be forced to comply with web standard The problem is that they ram whatever internal Chrome APIs they want through standards bodies and call it a standard. Others just can't keep up: https://web-confluence.appspot.com/#!/confluence https://web-confluence.appspot.com/#!/confluence
- dathinab 5y agoMaybe I should have called it "industry web standards" to explicitly exclude "google forced web standard"?
- deleted 5y ago[deleted]
- toiletaccount 5y agoMicrosoft got in trouble for less than this in the EU and had to start offering firefox as an option on standard installs. E: Just saw the /s in parent's grandchild.
- dathinab 5y agoSome of the problems come from codec licensing issues (which have a major competition hindering effect since over a decade? by now). But things come also from Google (and Microsoft, they seem to use the same logic) implementing some logic but based on "how the web standard" works but by "how it happens to work on chrome", this leads to frequent issues with selected input devices and screen sharing. And fixing it is easy, probably way less then 10h of work one single time. (As far as I know.) Similar the codec issues only matter if certain slow devices are involved, e.g. non high end phones, high end phones in energy saving mode, old tablets. If no such device is involved it's not rare that the conference will anyway use different codecs. So they could support FF for many conference calls, but instead they decide to reflect to even try to work on FF (which is a web no-go btw.). So there are "reasons", but it's clear that's they intend to not support FF at all. Btw. Microsoft is the worst here as they reject to work with FF even for things which do not have any reason to have problems on FF.
- approxim8ion 5y ago> If google devs code doesn't run as fast in firefox why should google take the blame ? And yet, I get flak if my code isn't performing well on 5 different browsers, including IE6.