3 ms·
Can you be specific about what exact features you think are so critical that the web would be better off without Safari? For example, if you've already retracte
by acdha 4y ago
Can you be specific about what exact features you think are so critical that the web would be better off without Safari? For example, if you've already retracted the claim down to “letting iOS users use PWAs which use more app-like features” it's clearly not true because most people do not use PWAs at all, even on Android, and there are many PWAs which work just fine.
> Additionally, I think you're mistaken on the performance crown. Firefox made big gains years ago but chrome has always managed to perform better at most tasks despite those gains.
This always comes down to which specific things you benchmark. All I can say is that I use Chrome, Edge, Firefox, and Safari on macOS, iOS, and Windows and it's exceedingly uncommon for Chrome/Edge to feel faster but I do notice their memory impact on the rest of the system. For battery life, Safari is hands down the winner followed by Firefox and then, distantly, the Chromium browsers.
- bioemerl 4y agohttps://wpt.fyi/results/ https://wpt.fyi/results/
- acdha 4y agoSo which specific features are that critical — for example, do you think most app developers can't work without the battery status API (or that users don't have a vested privacy concern)? I ask because when you drill into things like that there are a lot of numbers which look big until you realize that there are something like 57 tests for a non-standard API which is not broadly used even on the browsers which do support it.
- bioemerl 4y agoEvery feature has the potential to jump out and be critical, even ones that don't appear to be. Every time I try to use Safari to create something that goes beyond "display text" it's a new adventure in bugs and unsupported features that work in the other browsers. It's not one of those things you can sit and name, it's a 90/10 issue, and the margins are critical even though they appear small. Bugs surrounding drag and drop is what lead me to abandon all hope of supporting the browser some months ago.
- acdha 4y ago> Every time I try to use Safari to create something that goes beyond "display text" it's a new adventure in bugs and unsupported features that work in the other browsers. Do you have any examples which aren't so vague? The only times I've encountered this problem with other developers has been when they were using lots of Chrome-only features and put off testing in other browsers; when starting development in Firefox or Safari the most common case since around the early 2000s has been that everything works in the other two browsers with minimal effort.
- alwillis 4y ago> Every time I try to use Safari to create something that goes beyond "display text" it's a new adventure in bugs and unsupported features that work in the other browsers. Being hyperbolic doesn't help your case; it just looks like you're bashing WebKit because it's from Apple. And while you may have had a bad experience back in the day or don't like that Apple chooses not to implement esoteric or Chrome-only features, that doesn't mean that Safari sucks now. As I pointed out earlier in the thread [1], Apple has done a great job lately implementing features that they, Google, Mozilla and Microsoft have agreed should be implemented and interoperable and have W3C/WHATWG specifications. Every browser has bugs; the bug trackers for WebKit, Mozilla and Google are public, so we can actually see what they are. Like the other browser makers, Apple publishes its bug fixes when a new version of WebKit is released. [1]: https://news.ycombinator.com/item?id=33991256 https://news.ycombinator.com/item?id=33991256
- bioemerl 4y agoI'm not being hyperbolic, I'm being quite literal. I tried two or three times to support Safari. I gave up on it and I'm never going back. Not bashing web kit because it's from Apple, I'm bashing web kit because I had a website, I wanted to make that website support safari, and it was an absolute pain to the degree that I gave up on it. The only other browser I've had experiences like this in has been Firefox mobile. I have similar feelings about Firefox mobile. On the desktop, technically maybe Safari is fine on the desktop because I don't own a Mac so I can't test it, but chrome and Firefox are perfectly easy to make work together on the web with no issues. I do it everyday, safari is not normal in this.