3 ms·

Chrome gets closer and closer to becoming the new Internet Explorer in terms of browser interoperability, privacy, and lock in.

by dv_dt 5y ago

Rhedox 5y ago
To be fair Chrome is also far ahead of Firefox when it comes to performance and security (not to be confused with privacy). Safari is fast but compatibility is lacking, not just compared to Chrome.
- olliej 5y ago
  Yeah, but compatibility is already defined as "what chrome does". To be clear I mean quirks, not features. You can easily make objective comparisons on "does feature exist in browser Y" so I'll leave that as an exercise for the reader :D But "compatibility" is things like layout quirks, and before Chrome was the IE of the web, "correct behavior" was "what IE does". A lot of the IE escape was engineering effort devoted to developing IE compatibility. A chrome monopoly is going mean google has functionally complete control of the web, so they can simply state that their behavior is the spec. On top of that they already regularly force the addition of google identity based spying directly into the browser.
  - mmis1000 5y ago
    It 'is' already working in this way. Firefox do support a few WebKit prefixed api due to heavy usage by web developers (also because chrome never finalize them, let them keep prefixed) https://caniuse.com/css-line-clamp https://caniuse.com/css-line-clamp
SahAssar 5y ago
Not even close. IE did things like include directx filters (which obviously need directx to work), activex, choose a non-standard box-model (which webdevs might choose these days, but back then there was no choice) and many, many more things. I don't like chrome and especially on the privacy front it's bad but they usually try to make sure that their features are at least technically adoptable by other platforms. We don't have to call a browser "the new IE" to argue against their anti-features.

3 ms·

Chrome gets closer and closer to becoming the new Internet Explorer in terms of browser interoperability, privacy, and lock in.

by dv_dt 5y ago

Chrome gets closer and closer to becoming the new Internet Explorer in terms of browser interoperability, privacy, and lock in.

Rhedox 5y ago
To be fair Chrome is also far ahead of Firefox when it comes to performance and security (not to be confused with privacy). Safari is fast but compatibility is lacking, not just compared to Chrome.
- olliej 5y ago
  Yeah, but compatibility is already defined as "what chrome does". To be clear I mean quirks, not features. You can easily make objective comparisons on "does feature exist in browser Y" so I'll leave that as an exercise for the reader :D But "compatibility" is things like layout quirks, and before Chrome was the IE of the web, "correct behavior" was "what IE does". A lot of the IE escape was engineering effort devoted to developing IE compatibility. A chrome monopoly is going mean google has functionally complete control of the web, so they can simply state that their behavior is the spec. On top of that they already regularly force the addition of google identity based spying directly into the browser.
  - mmis1000 5y ago
    It 'is' already working in this way. Firefox do support a few WebKit prefixed api due to heavy usage by web developers (also because chrome never finalize them, let them keep prefixed) https://caniuse.com/css-line-clamp https://caniuse.com/css-line-clamp
SahAssar 5y ago
Not even close. IE did things like include directx filters (which obviously need directx to work), activex, choose a non-standard box-model (which webdevs might choose these days, but back then there was no choice) and many, many more things. I don't like chrome and especially on the privacy front it's bad but they usually try to make sure that their features are at least technically adoptable by other platforms. We don't have to call a browser "the new IE" to argue against their anti-features.