5 ms·
from the caniuse data, it looks like Safari might actually be working on this? Which is both hugely surprising and deeply concerning, given their track record
by tehbeard 5y ago
from the caniuse data, it looks like Safari might actually be working on this?
Which is both hugely surprising and deeply concerning, given their track record with both implementing APIs and the stability/reliability of them.... The tinfoil hat me in says they might fuck it up to justify the apple ecosystem stance of app store or nothing.
- eyelidlessness 5y agoPut down the tinfoil, the WebKit team has been on a tear recently and very actively hiring to keep that momentum and very actively seeking feedback. Regardless of Apple’s priorities, Safari is very much on an improvement track
- hnbad 5y agoI think a more justified and nuanced criticism is that Apple is harming the web by tying Safari updates to macOS and iOS updates, which makes the criticism of Safari being the new IE a lot more justified (now that IE has been replaced by the evergreen cross-platform Edge). Safari might get more frequent and broader updates but that's no use when people are still using older versions of macOS and iOS and might be stuck with it (especially with fresh memory of Apple intentionally slowing down iOS devices to encourage buying new hardware).
- shuckles 5y agoSafari on macOS is supported two major OSes releases back. The latest iOS is supported on iPhones launched in 2015 and later. How many users on older versions of Safari are limited by OS version?
- eyelidlessness 5y agoTo some extent this is a fair criticism, and I certainly wish Safari were less tied to OS releases. That said, iOS users tend to update about as quickly as you could hope for (and update hardware often enough that being left behind is uncommon), and macOS users who lag behind tend to use Chrome anyway.
- deleted 5y ago[deleted]
- dmitriid 5y agoWhere Chrome is fast and loose with APIs, Safari and Mozilla actually stop and think before implementing them.
- synergy20 5y agoCan't macos use chrome for file-access-api instead if Safari does/will not support it? Same issues with PWA support as far as I can tell, maybe Macos users just install chrome and use that too?