4 ms·
>for those of us that don't use chrome, Sure, but that's like being one of the tribes of Europe before the Romans. When the tribes got crushed and everyone be
by treis 6y ago
>for those of us that don't use chrome,
Sure, but that's like being one of the tribes of Europe before the Romans. When the tribes got crushed and everyone became Roman peace and prosperity (mostly) reigned. Having to use chrome if you don't want to sucks, but it makes things way easier for developers to have one browser to target.
- pyrale 6y ago> When the tribes got crushed and everyone became Roman peace and prosperity (mostly) reigned. Well, it didn't really go well for the tribes. About half of the gallic population was killed or enslaved. As for the romans, that war was started to reinforce the personal power of Caesar, and the power imbalance it generated led to the fall of the republic. I'm not sure your historic analogy makes a great case for your point. > it makes things way easier for developers to have one browser to target. What makes things easier for developers is standards. As for targetting one product present in a walled garden, it may be pleasant in the short term, but we have many cautionary tales about it, and Google is responsible for more than their fair share of them.