Re:Google proposes changes to Chromium which would disable u...
by AsyncAwait on Wednesday January 23, 2019 @06:22AM
(#18977349)
> Is that really relevant?
Kind of, only because Google uses the ShadowDOM API to break its product on competing browsers and playing into it will only reinforce this behavior.
Using both for years, Chrome has just been faster and more reliable. I don't do web dev professionally, but I use multiple browsers in tandem and often try to use one full time every once in awhile. On my old laptop, I'm pretty sure Chrome was the only one to support webGL for whatever reason. At work we're stuck with Firefox 38.3.0 ESR (Cent6/7) and Prometheus Alert Manager (and I also believe Prometheus graphing interface) has broken widgets, but Chrome works. Chrome has always seemed to better support the very few websites that require crazy performance. This was even the case when we would have an ancient version of Chrome and a new version of Firefox. It sucked when Firefox switched plugin architecture and Google Hangouts never added support. Now Google Meet does not support Safari.
I'm not saying any of these comparisons are "fair" but its what I deal with day-to-day.