4 ms·
> Chrome follows 10s possibly even 100s of standards that Safari is dropping the ball on. I went almost full Apple 14 months ago and I am yet to find a single
by pdimitar 8y ago
> Chrome follows 10s possibly even 100s of standards that Safari is dropping the ball on.
I went almost full Apple 14 months ago and I am yet to find a single website that I need that's not working at all or even well enough in Safari, desktop or mobile.
The only argument I've seen so far is "but standard X is new, we need it!" without ever saying why do you need it.
Care to elaborate?
- saagarjha 8y ago> I am yet to find a single website that I need that's not working at all or even well enough in Safari, desktop or mobile. This isn't a particulary great argument, since web developers are generally forced to adopt the lowest common denominator of what popular browsers implement.
- pdimitar 8y ago"We need the latest standards" isn't a particularly great argument either. Web existed and flourished long before 90% of these new standards even came into being.
- Semaphor 8y agoUmh, for a long time people could use old IEs and say the same. I assume IE11 people will also not have any problems. Yet IE11 is why many people will not be able to use CSS Grid for a long time. Your argument makes no sense unless you say you WANT devs to exclude people with left-behind browsers.
- pdimitar 8y agoYou are shifting the topic with a flawed analogy. IE was breaking websites left and right. Safari doesn't. Give me an example of Safari users getting significantly worse experience in a web service that they need in their everyday lives.
- Semaphor 8y agoI'm not. I'm telling you why your argument makes no sense. People don't use features that would break safari.