4 ms·

Maintaining web standards without breaking backwards compatibility is literally what they signed up for when they decided to make a browser. If they didn't wan

Maintaining web standards without breaking backwards compatibility is literally what they signed up for when they decided to make a browser. If they didn't want to do that job, they shouldn't have made one.

will4274 1y ago
According to whom? Chromium is open source and free (both as in beer and speech). The license says they've made no future commitments and made no warrants. Google signed up to give something away for free to people who want to use it. From the very first version, it wasn't perfectly compatible with other web browsers (which mostly did IE quirks things). If you don't want to use it, because it doesn't maintain enough backwards compatibility... Then don't.
- lunar_mycroft 1y ago
  The license would be relevant if I'd claimed that removing XSLT was illegal or opened them up to lawsuits, but I didn't. The obligation they took on is social/ethical, not legal. By your logic, chrome could choose to stop supporting literally anything (including HTML) in their "browser" and not have done anything that we can object to. iIRC, lack of IE compatibility is fundamentally different, because the IE specific stuff they didn't implement was never part of the open web standards, but rather stuff Microsoft unilaterally chose to add.
  - will4274 1y ago
    > By your logic, chrome could choose to stop supporting literally anything (including HTML) in their "browser" and not have done anything that we can object to. Literally this. Microsoft used to ship a free web browser. Then they stopped. That's not something anybody can object to. > because the IE specific stuff they didn't implement was never part of the open web standards, but rather stuff Microsoft unilaterally chose to add. Standards aren't holy books. It's actually more important to support real customer use cases than to follow standards. But you know this. If standards are more important that real use cases, then the fact that XSLT has been removed from the html5 standard is enough justification to remove it from Chrome.
    - lunar_mycroft 1y ago
      > Literally this. Microsoft used to ship a free web browser. Then they stopped. That's not something anybody can object to. There is a fundamental difference between ceasing to make a browser and continuing to make a browser, while not meeting your expectations as a browser maker. > If standards are more important that real use cases, then the fact that XSLT has been removed from the html5 standard is enough justification to remove it from Chrome. Browsers very much have not depreciated support for non-HTML5 markup (e.g. the HTML4 era <center> tag still works). This is because upholding devs and users expectation that standards compliant websites that once worked will continue to work is important.
  - shadowgovt 1y ago
    We object with our feet, by switching browsers. What odds would you put dropping XSLT support at for triggering a user migration?
- spookie 1y ago
  The license is the way it is not by choice. We should be clear about that and acknowledge KHTML, and both Safari and Chromium origins. Some parts remain LGPL to this day.
spookie 1y ago
They "own the web". They steer its standards, and other browsers' development paths (if they want to remain relevant). It is remarkable the anti-trust case went as it did.
deleted 1y ago
[deleted]
deleted 1y ago
[deleted]

will4274 1y ago

According to whom? Chromium is open source and free (both as in beer and speech). The license says they've made no future commitments and made no warrants. Google signed up to give something away for free to people who want to use it. From the very first version, it wasn't perfectly compatible with other web browsers (which mostly did IE quirks things). If you don't want to use it, because it doesn't maintain enough backwards compatibility... Then don't.

lunar_mycroft 1y ago
The license would be relevant if I'd claimed that removing XSLT was illegal or opened them up to lawsuits, but I didn't. The obligation they took on is social/ethical, not legal. By your logic, chrome could choose to stop supporting literally anything (including HTML) in their "browser" and not have done anything that we can object to. iIRC, lack of IE compatibility is fundamentally different, because the IE specific stuff they didn't implement was never part of the open web standards, but rather stuff Microsoft unilaterally chose to add.
- will4274 1y ago
  > By your logic, chrome could choose to stop supporting literally anything (including HTML) in their "browser" and not have done anything that we can object to. Literally this. Microsoft used to ship a free web browser. Then they stopped. That's not something anybody can object to. > because the IE specific stuff they didn't implement was never part of the open web standards, but rather stuff Microsoft unilaterally chose to add. Standards aren't holy books. It's actually more important to support real customer use cases than to follow standards. But you know this. If standards are more important that real use cases, then the fact that XSLT has been removed from the html5 standard is enough justification to remove it from Chrome.
  - lunar_mycroft 1y ago
    > Literally this. Microsoft used to ship a free web browser. Then they stopped. That's not something anybody can object to. There is a fundamental difference between ceasing to make a browser and continuing to make a browser, while not meeting your expectations as a browser maker. > If standards are more important that real use cases, then the fact that XSLT has been removed from the html5 standard is enough justification to remove it from Chrome. Browsers very much have not depreciated support for non-HTML5 markup (e.g. the HTML4 era <center> tag still works). This is because upholding devs and users expectation that standards compliant websites that once worked will continue to work is important.
- shadowgovt 1y ago
  We object with our feet, by switching browsers. What odds would you put dropping XSLT support at for triggering a user migration?
spookie 1y ago
The license is the way it is not by choice. We should be clear about that and acknowledge KHTML, and both Safari and Chromium origins. Some parts remain LGPL to this day.

spookie 1y ago

They "own the web". They steer its standards, and other browsers' development paths (if they want to remain relevant). It is remarkable the anti-trust case went as it did.

deleted 1y ago

[deleted]

deleted 1y ago

[deleted]