A list of recent hostile moves by Google's Chrome team

Re:A list of recent hostile moves by Google's Chrome team by mrtksn on Thursday August 03, 2023 @05:08AM (#36983273)

The reason IE was hated for being tied in the OS was because the OS was crashing due to the IE bugs. That's not the case with macOS or iOS at all, just because the OS provides a JS engine out of the box doesn't make it Windows Me grade.

[ Parent | on HN ]

Re:A list of recent hostile moves by Google's Chrome team by TheDong on Thursday August 03, 2023 @05:19AM (#36983340)

> because the OS was crashing due to the IE bugs. That's not the case with macOS or iOS at all

I mean, I've had iOS crash while using safari more often than I had windows 98 crash while using IE.

At least back in the IE days, when a user found a site they couldn't open in IE, they could go download firefox.

When a user encounters a websites that doesn't work on iOS safari, they can't download a different browser.

Even worse, when you report the bug to the site owner (say your friend), they'll then say "Oh, sorry, I don't own an iPhone or macbook, so I'd have to pay $800+ to reproduce your bug", while with IE, it ran on basically any computer, and I think windows back then still had a trial version you could use for free.

[ Parent | on HN ]

Re:A list of recent hostile moves by Google's Chrome team by Semaphor on Thursday August 03, 2023 @05:17AM (#36983334)

I disagree. It made it, so people with an older OS could not get a current IE. So you had ancient IE version linger for years and years.

And with Safari, I can’t test any specific issues because we only have one mac, and it’s old and can’t run a current Safari. The situation is slightly better than with IE, as multiple macOS versions apparently (or so I was told) can run a newer Safari, but still not all.

[ Parent | on HN ]