4 ms·

I would happily rather that neither of these happen. For safari not to be a buggy mess/work without extra development efforts and for chrome to have real compe

I would happily rather that neither of these happen. For safari not to be a buggy mess/work without extra development efforts and for chrome to have real competition enough to prevent them setting a standard. I will however, take chrome and user choice every single day over Safari's monopolistic crap. The mere fact it's largely successful by it's nature of being bundled should scream to you how bad it really is.

kitsunesoba 4y ago
> I will however, take chrome and user choice every single day over Safari's monopolistic crap. That's the problem, though: more and more as time goes on, Chrome isn't user choice. Sites that only work with or only perform as expected under Chrome are becoming more and more common. It's becoming a monopoly too, but enforced by developers rather than a platform owner (though this is muddy with how Google gives Chrome performance advantages in Youtube, Docs, etc), and I'm not sure it's really any better.
- illiarian 4y ago
  > though this is muddy with how Google gives Chrome performance advantages in Youtube, Docs, etc When (mostly) Chrome came up with Web Components, they immedieately re-wrote Youtibe with Web Components v0 (now deprecated). The polyfill for them was infamously slow on Firefox. Just another ooops in a long line of oopses: https://twitter.com/johnath/status/1116871237240852480 https://twitter.com/johnath/status/1116871237240852480