2 ms·
When IE had a monopoly it was bad because Microsoft made a shitty webbrowser and everyone built websites for IE. Even today I have devices which are "best view
by zaarn 7y ago
When IE had a monopoly it was bad because Microsoft made a shitty webbrowser and everyone built websites for IE.
Even today I have devices which are "best viewed on IE6", thanks to modern browsers they still tend to work somewhat.
Chrome will not be bad because it's a shitty browser, it'll be bad because Google can force features into standards and essentially do what they want with no recourse.
It's not the developers fault directly but they inherently support an abusive vendor-user relationship.
Everyone who doesn't see that is just a Google-apologist.
- cookie_monsta 7y ago> it'll be bad because Google can force features into standards and essentially do what they want with no recourse. Again, not the way it worked with IE 1-8 > Everyone who doesn't see that is just a Google-apologist. Well I don't and I'm not.
- zaarn 7y agoAnd again, that's what Google is already doing, I'm not saying they're doing the exact same things that happened with IE1-8 but a browser monopoly is still equally bad regardless of how badly a browser is maintained.
- cookie_monsta 7y agoOh, absolutely - I'm not arguing in favour of browser monopolies. I'm saying that browser standards aren't a popularity contest. You can have the most popular browser in the world but still not be able to strongarm your way into compliance. Remember attachEvent?
- zaarn 7y agoWell, those are to some extend exceptions, if a browser has major marketshare, then any change implemented will have to be implemented by others. Google doesn't have to stop implementing them at all, no matter the response from devs.