top | item 42327036

(no title)

celso | 1 year ago

How is Safari "behind" modern standards? Seems pretty up to date, if not ahead in come cases, to me.

https://caniuse.com/?compare=chrome+134,safari+18.2,firefox+...

discuss

order

tucnak|1 year ago

See the last table. By what extent of imagination it is "up to date"? Not to mention that many "Partials" in the second table are really more on the "No" side, like Push API. But yeah, it's not even the matter of WebGPU, or whatever, Safari doesn't support SVG favicons still...

P.S. Surprised how far back Firefox had fallen, actually.

shellac|1 year ago

The last table is an awful lot of chrome only bits, many of which are a pretty bad idea on the web.

spiderfarmer|1 year ago

By the most reasonable extent of my imagination: daily usage, the browser is the best of all available. It’s super fast, super stable and not spyware. It’s also great fit for the ecosystem.

ninkendo|1 year ago

Ah yes, the "Vibration API", I really wish Safari had that. And the Web MIDI API, and Web Bluetooth, Web Serial, etc etc.

The vast majority of these are APIs that I explicitly do not want websites to use. Especially things like "touch events", which would serve to allow websites to implement their own dumbass broken scroll implementations (again, this is very intentionally not supported.) It would seem Apple is very intentional in choosing not to support most of these.

There is only one reason these APIs exist at all, and it is that Google has decided to make their browser into an OS (chromeOS) and so they need to invent a web API for everything a normal OS may need to do, so that "everything is a webapp" can be a sorta half-true thing. They exist because Google crammed them through standards committees that they have essentially a majority vote on.