3 ms·
Multiple implementations help the web be diverse, and there is a long history of features becoming easier to use, more capable, or secure based on feedback from
by acdha 4y ago
Multiple implementations help the web be diverse, and there is a long history of features becoming easier to use, more capable, or secure based on feedback from one of the browser teams other than the first to propose something.
It’s also not the case that any current browser is so bad that the web is better off without it. Anyone with web development experience has run into problems or limitations with every browser and depending on what you do you will have different assessments of which one is best at a given time. For example, on the Interop 2022 effort all three browser teams have been coordinating currently Safari is in the lead and that will continue to shift over time.
https://wpt.fyi/interop-2022 https://wpt.fyi/interop-2022
> When is the last time you said "I will choose to use safari" or seen apple pushing the bounds of what the web can do?
Firefox and Safari are both noticeably faster and use less memory. If you care about that, or work on battery that’s enough right there.
Firefox and Safari don’t have conflicts of interest preventing privacy improvements or ad blocking.
I haven’t used Chrome as my default browser since Firefox took the performance crown ~5 years ago but I’ve used all of them plenty as a web developer. The idea that Chrome is so far ahead that we should give up on the web having multiple implementations and just let Google run it is completely the opposite of my experience.
- bioemerl 4y ago> It’s also not the case that any current browser is so bad that the web is better off without it. But it is. Safari on IOS is either missing or badly implements every system that lets web apps compete with system apps. It's totally impossible to use something other than safari on IOS as well, which basically means apple is able to force a very significant amount of web traffic into their browser and basically lock out any feature the choose. That is bad for the web. 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. Maybe if you were running really low on ram Firefox is the faster option? That's not your typical use case though. I use Firefox regardless. I way value their not crippling AdBlock over chrome and would encourage everyone to use it despite speed issues.
- acdha 4y agoCan 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.