Neither is Safari. Safari is actually part of the solution. Safari has saved Firefox and other browsers by being the only option on iOS for a long time and a better choice for many (because of battery usage) on Mac OS. Without Safari I am afraid we would all be locked into Chrome now.
The problem is that Google, like Microsoft before them,
1. used their dominant position in one market to force their way into dominating another market,
2. used various underhanded tactics to make users think Chrome were better while in reality it was just given better treatment by their backend servers and also the Googles frontend devs[1]
3. and that unlike Microsoft they still haven't got a multi billion fine for it and haven't been forced to advertise alternative browsers for months.
[1]: see various bugs[2] in everything from the core of the Angular framework to Google Calendar to YouTube
[2]: yes, I am generous enough to consider them bugs. I am fairly certain though that bugs that doesn't affect Chrome aren't exactly considered top priority.
> Google, like microsoft, <1-3>
If you're going to complain about 1-3 for google and ms, I don't think you can praise safari in the same breath.
Apple's abused their position with the iPhone to make safari relevant, and unlike Chrome and IE, users can't just install another browser.
Apple's behavior is the only reason I can't run my own addons I've written for firefox on iOS (they run _fine_ on android of course), why I can't run uBlock origin on iOS, and so on.
Apple's behavior on iOS is far more egregious than anything microsoft or google has ever done.
I never once had to run IE or Chrome unwillingly since I could always install netscape, or mosaic, or firefox.
I'm forced to run Safari, unable to decently block ads, unable to use the adons I've written, unable to fork and patch my browser to fix bugs, and I've generally had my software freedoms infringed... and if I don't run safari, then I can't talk to my family group chat (no androids allowed, sms breaks the imessage group features too much) or talk to my grandma who only knows how to use facetime.
I wish so much I could use a phone with firefox, but I can't justify having a spare iPhone just to talk to my family, so I'm kinda forced to suffer through safari, held hostage by apple's monopolistic iMessage behavior.
The only thing that comes close to Apple's behavior is Google's campaign to force Chromebooks upon children in classrooms, requiring them to use Chrome, but at least Google isn't holding their grandmother's hostage... and managed work/school devices already are kinda expected to have substantially less freedom than personal devices, so it feels much less egregious.
Amazing. https://en.m.wikipedia.org/wiki/1984_(advertisement)
But more seriously: it is actually the truth.
Kind of in in the same way that people are thankful for Churchill: not because he was a fantastic man in every way (he wasn't) but because he saved us from something even worse.
I even thought it wasn't necessary to test them separately but I recently heard from someone with more and more recent experience that some differences exist, particularly around prefixed css attributes. Can't say for sure though, but that was why I wrote my comment above somewhat defensively.
How is MIT any worse at preventing this, when GPL didn't?
B: "Ah I see that means we should just give up all measures, instead of you know advocating for stronger measures or anything else obvious and logical like that."
This only means we must start any projects today with stronger GPL or similar variants such as AGPL.
You had a security breach, despite using a better set of technologies and techniques.
During the postmortem, you suggest this means we should give up all security or just use the weaker solution, since its all the same, the server would have gotten breached in either case.
Instead of advocating for building a stronger security.