3 ms·
It's free and runs nearly everywhere, so the consequences don't seem quite the same?
by skybrian 6y ago
It's free and runs nearly everywhere, so the consequences don't seem quite the same?
- rebolek 6y agoInternet Explorer was also free and run nearly everywhere as Windows were on 98% machines.
- hackerbrother 6y agoI do think it being cross-platform and open-source is a significant difference.
- rebolek 6y agoAnd I do think that using their market share to push "standards" no-one else agreed on is what actually makes them the new MS/IE. Should Firefox just catch upon what Chrome already has implemented or should the standards be decided by a standard body? You can believe the first one is true, I do not.
- hackerbrother 6y agoI agree with you. All i’m saying is it’s good that Blink isn’t a black box unlike IE.
- sebazzz 6y agoChrome is not open source. Chromium is - but it is not the exact same build.
- fgonzag 6y agoYou probably didn't suffer through IE and active X
- mufufu 6y agoIE was free as well, didn't prevent it from turning into a pile of garbage when it controlled like 90% market share, which in turn affected everyone (consumers, developers, etc..)
- shadowgovt 6y agoIE required an operating system I paid money for. I can run Chromium on Linux with no layout of cash.
- the_other 6y agoIt doesn’t run on my phone. Even if it did run on my phone, I wouldn’t run it, because Google. Now, on the one hand, this is just me being an annoying, Apple fanboy, tracking-resistant outlier. But on the other hand, “you” targeted the web BECAUSE it’s the open platform for the widest range of users. “You” decided against a native app so as to cut costs and produce a more consistent/responsive cross-platform application. “You’ve” already saved the money it would have cost you to support multiple OSs. Use some of that saving to support the web.
- joombaga 6y ago> Use some of that saving to support the web. Or don't. I don't get mad when people write bash-specific scripts that won't work on all POSIX compliant shells. This seems analogous (though admittedly non-compliance to web standards has a larger impact than non-compliance to shell standards). Perhaps Chrome removed enough barriers for the tool to exist at all.