(no title)
riolu | 3 years ago
Safari existing has never held anyone back. The "plausible solution" is to be patient for Apple to implement AV1.
riolu | 3 years ago
Safari existing has never held anyone back. The "plausible solution" is to be patient for Apple to implement AV1.
p1necone|3 years ago
This still isn't really a problem (if it gets bad enough, devs will just stop supporting it), except for on iOS where it's the only browser available, so not supporting them is not an option.
alwillis|3 years ago
Safari was the first browser to ship the most anticipated web feature of the last 3-4 years by web developers: the parent selector :has() [1] back in March.
When you check the Interop 2022 dashboard [2], Safari Technology Preview is ahead of both Firefox nightly and Chrome dev for the shipping the latest web features. Safari Technology Preview is passing 97% of the interop tests.
In case nobody noticed, the WebKit team kicked ass by shipping a ton of new features this year:
* dialog element
* lazy loading
* inert
* :has() pseudo-class
* new viewport units
* Cascade Layers
* focus visible
* accent color
* appearance
* font palettes for color fonts
* BroadcastChannel
* Web Locks API
* File System Access API
* enhancements to WebAssembly
* support for Display-P3 in canvas
* additions to COOP and COEP
* container queries
* subgrid
* web push
* shared workers
* CSS Offset Path
* AVIF
* Passkeys
Plus it’s faster and has better battery life on macOS than either Chrome or Firefox. What’s not to like?
[1]: https://webkit.org/blog/12445/new-webkit-features-in-safari-...
[2]: https://wpt.fyi/interop-2022
MBCook|3 years ago
See I’m not so sure that’s a problem. Many of the things they haven’t added I’m glad they didn’t. I like that they aren’t just rushing to implement everything someone proposes or a competitor ships.
I don’t think that’s a bad thing.