[ocdtrekkie]

So, the issue is that the "innovation" Safari is often accused of "holding back" is privacy-invasive features proposed by Google engineers.

Which is to say, Safari (and the requirement of iOS users using it) is the last thing holding back Google from complete control of the web at this point.

[rejhgadellaa]

Which features are we talking about? Bluetooth? NFC? Contacts? Because native apps enjoy all of them, AFAIK. These same features tend to have extra protections built in that native apps do not to ensure privacy and security. The web is extremely paranoid when implementing these features.

From what I've learned, WebKit is not engaging in discussions regarding these new features. They could have a say in shaping the web, come up with alternatives, new features, etc. Instead they dig in their heels.

If Safari needs "the requirement of iOS users using it" to hold back Chrome, it tells us people actually want to switch.

Letting Apple decide what's best for us (for reasons that have nothing to do with "what's best for us", I think is safe to assume) is not the solution for the monolith browser problem we're seeing.

[theo-steiner]

I built a "creative" website over the last few months. I had to jump through many hoops to get very standard css behavior to work on safari. Transform scale for example leads to text being rendered pixelated while transformZ is not 0. Firefox and Chrome don't have this bug, which has been around for years on Safari. Last time I checked, CSS was not privacy invasive.

[mindblock]

Agreed. I've had display: flex make a component inline on random elements in a web app. No discernible reason whatsoever, just some flex elements dont appear on the screen as boxes. There's a reason web devs say Safari is the new IE.