4 ms·
It is indeed very likely going to die. Webkit team isn't even considering it anymore now.
by nobodyshere 7y ago
It is indeed very likely going to die. Webkit team isn't even considering it anymore now.
- stabbles 7y agoDo you have a source for that?
- guzik 7y agoI think he refers to https://webkit.org/status/#?status=not%20considering https://webkit.org/status/#?status=not%20considering
- nobodyshere 7y agoSorry for not linking it. Thank you guzik for doing what I should've done. That's the link I meant.
- neoeldex 7y agoWebkit itself is very likely to die xD. Who uses safari nowadays?
- kleptako 7y agoiOS users
- realusername 7y agoI would not say it's likely to die because it's obviously false since on iOS it's the only choice but it's true that when you see the release logs of Safari, it's moving very slowly very far behind Chrome or Firefox.
- shantly 7y agoAnyone on macOS who values battery life and system responsiveness.
- simonklitj 7y agoSafari has 15% of the browser market share (https://gs.statcounter.com/browser-market-share https://gs.statcounter.com/browser-market-share) (including mobile). WebKit will probably be fine for the foreseeable future.
- Ajedi32 7y agoWebkit is missing a _lot_ of useful features. Safari not implementing something doesn't have to mean its dead. It just means iOS users will be forced to download a separate app to interact with Bluetooth devices via the web.
- nobodyshere 7y agoDo they provide such a low level API to usual mortal developers? This isn't going to be nice and comfy in terms of usability if it happens the way you describe.