3 ms·
> Developers are eating the problems for you because safari support is almost always a requirement. The problems "developers are eating" are hugely overblown
by illiarian 4y ago
> Developers are eating the problems for you because safari support is almost always a requirement.
The problems "developers are eating" are hugely overblown
> Safari never breaks, but when it does it's because the developers are incompetent?
In 99% of the times? Yes.
> The fact it takes a bunch of extra work to support safari
No, it doesn't. Source: web developer myself.
Of course, if you rely on Chrome-only non-standards, that's a different issue.
> in more advanced cases like graphs and dashboards
Graphs and Dashboards are advanced use cases now. Gotcha.
- bioemerl 4y agoYou should reconsider your position when your only response is dismissal and insult.
- illiarian 4y ago> You should reconsider your position when your only response is dismissal and insult. I've been in these threads many times, and it's the same thing again and again: - Safari is holding back the web! It doesn't. Well, if you think that Chrome is web, then you're entitled to your opinion - Safari is new IE! It's not. That it doesn't implement the 400 or so APIs a year that Chrome implements is a feature, not a bug. If your site ends up with a "only works in Chrome" badge, that is your new IE - Chrome split from WebKit three years after WebKit appeared. And the only reason for the split? Well, to do the same thing you accuse Apple and MS of doing: control. And look how well it worked for them. Everything they do is now considered standard and gospel by the gullible masses of web devs. And so on. The irony is that it's Chrome that breaks the web often, and badly, but they get a pass because it's Chrome! They have the new shiny APIs!
- Kiro 4y agoYou're just being obnoxious. Stop it.