3 ms·

> Microsoft was actively developing IE and had good intentions after it won the browser war Ahahahaha yeahhh you lost me at that ridiculous and baseless claim.

> Microsoft was actively developing IE and had good intentions after it won the browser war Ahahahaha yeahhh you lost me at that ridiculous and baseless claim. https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguish https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis... And speaking as someone who had to develop for it, making a site both IE-compatible (around versions 5 thru 8) AND compatible with any other browser LITERALLY DOUBLED THE WORKLOAD. They made absolutely no effort to conform to standards by design because it forced companies (and there were many) to develop "IE-primarily" sites. That experience alone gave me a lifetime of hate for Microsoft.

micahdeath 4y ago
And now Chrome does the same thing.
- EugeneOZ 4y ago
  Could you please confirm it using caniuse.com? I don't see red squares often in the “Chrome” column there (only some really ancient versions).
  - hakre 4y ago
    Take this perspective: The less boxes in a row, the less complex. Can I use is biased towards feature creep. If not supporting a feature (in terms of not having it, not half implemented) would count and this would be visually faire represented, what we be your choice?
    - EugeneOZ 4y ago
      I’m not choosing a browser here, I’m saying that Chrome is not repeating the most fatal mistake of IE: implementing many APIs in their own way, often very different from the standard. Until recently, Safari was repeating the IE approach, but right now it looks like they turned to the road of sanity.
  - bytesandbots 4y ago
    Isn't that Chrome's entire game? Keep developing new APIs into standards even before they are standardised such that everyone else is always just trying to keep up. Advertise these new APIs to web developers such that new websites only work well in Chrome.
    - EugeneOZ 4y ago
      What is wrong with this approach? They are not breaking the standards as IE did. It was the only issue with IE. What is an alternative - always wait while some API is implemented by other browsers first? It's not their fault they are faster. Disclaimer: I have ZERO relations with Google, Chrome, or Chromium.
- pmarreck 4y ago
  You have a point, they're balking on implementing JPEG-XL, probably due to NIH syndrome

micahdeath 4y ago

And now Chrome does the same thing.

EugeneOZ 4y ago
Could you please confirm it using caniuse.com? I don't see red squares often in the “Chrome” column there (only some really ancient versions).
- hakre 4y ago
  Take this perspective: The less boxes in a row, the less complex. Can I use is biased towards feature creep. If not supporting a feature (in terms of not having it, not half implemented) would count and this would be visually faire represented, what we be your choice?
  - EugeneOZ 4y ago
    I’m not choosing a browser here, I’m saying that Chrome is not repeating the most fatal mistake of IE: implementing many APIs in their own way, often very different from the standard. Until recently, Safari was repeating the IE approach, but right now it looks like they turned to the road of sanity.
- bytesandbots 4y ago
  Isn't that Chrome's entire game? Keep developing new APIs into standards even before they are standardised such that everyone else is always just trying to keep up. Advertise these new APIs to web developers such that new websites only work well in Chrome.
  - EugeneOZ 4y ago
    What is wrong with this approach? They are not breaking the standards as IE did. It was the only issue with IE. What is an alternative - always wait while some API is implemented by other browsers first? It's not their fault they are faster. Disclaimer: I have ZERO relations with Google, Chrome, or Chromium.
pmarreck 4y ago
You have a point, they're balking on implementing JPEG-XL, probably due to NIH syndrome