[baggy_trough]

What are the "ever growing set of standards" that Safari doesn't support?

[arbitrarian]

This was discussed here not too long ago. I assume not much has changed since then. https://news.ycombinator.com/item?id=31902707

[threeseed]

Most of those that were discussed have been implemented. The new list is here [1].

What you see is that they implement different features with Google obviously wanting the browser to be a full blown OS. So they added things like MIDI support and web pages being able to access the battery.

The problem with many of those features is that they have been shown by researchers to either (a) be insecure or (b) allow web pages to uniquely fingerprint your device. This is obviously an anathema to everything Apple believes in.

[1] https://caniuse.com/?compare=chrome+121,edge+118,safari+17.2...

[troupo]

Firefox is also against many of the hardware APIs that Chrome pushes

[baggy_trough]

So you don't know, but you assume it's the same, so "ever-growing" is just a uninformed slam? If anything the reality is the opposite.

[asylteltine]

Nothing that is relevant. I use safari across all my devices and I have never had an issue besides very specific things like flashing microcontrollers through a web interface which I had to use chrome for. That’s basically irrelevant for the entire world. Safari is mega efficient and fast and actually cares about your privacy

[alwillis]

There was so much hoopla on HN about Chrome abandoning JPEG XL recently while Safari added support for it.