3 ms·

> while a page (doing more advanced things) not built for safari simply will not work in safari. I've yet to see such a page [1]. And I've been using Safari si

> while a page (doing more advanced things) not built for safari simply will not work in safari. I've yet to see such a page [1]. And I've been using Safari since 2007 [1] Unless it's built with Chrome's non-standards of course. Edit: of course there will be pages broken in Safari (or FF) for no reason other than the sheer incompetence of people building them. E.g. we have an internal dashboard page that is literally nothing more than tables and charts. Ooops, "only works in Chrome". There's also the minor case of nominally open audio and video codecs that Google pushes to device manufacturers on pain of removing access to its services, but even that hasn't affected me, or most people really, that much.

bioemerl 4y ago
> I've yet to see such a page Developers are eating the problems for you because safari support is almost always a requirement. This is a developer side problem, not a user side one. > for no reason other than the sheer incompetence of people building them Safari never breaks, but when it does it's because the developers are incompetent? The fact it takes a bunch of extra work to support safari (in more advanced cases like graphs and dashboards) is the whole problem. I have every intent to kick safari out of any home game stuff I do.
- 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 ago
    You 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 ago
        You're just being obnoxious. Stop it.

bioemerl 4y ago

> I've yet to see such a page Developers are eating the problems for you because safari support is almost always a requirement. This is a developer side problem, not a user side one. > for no reason other than the sheer incompetence of people building them Safari never breaks, but when it does it's because the developers are incompetent? The fact it takes a bunch of extra work to support safari (in more advanced cases like graphs and dashboards) is the whole problem. I have every intent to kick safari out of any home game stuff I do.

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 ago
  You 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 ago
      You're just being obnoxious. Stop it.