3 ms·

That is because Safari's feature support is the lowest common denominator of the other browsers. By developing on it you are ensuring you don't use features eve

by n42 9y ago

That is because Safari's feature support is the lowest common denominator of the other browsers. By developing on it you are ensuring you don't use features every other browser but Safari supports.

protobuflol 9y ago
Unless of course you're referring to ES6 support, in which case it has the best support.
- n42 9y ago
  You're probably right, I only have to deal with CSS inconsistencies since JS tooling largely solves that problem for me these days. Unfortunately tools like CSS prefixer can't solve for everything.
  - protobuflol 9y ago
    Totally. Anecdotally, though, a) firefox diverges further from chrome than safari does and b) the types of CSS flaws don't wven approach the black magic of designing for IE6.
ddebernardy 9y ago
> By developing on it you are ensuring you don't use features every other browser but Sure. But isn't developing against the least common denominator precisely what web development has been all about in the past 20 years or so? Edit: Just to expand on that... Then, there was a laundry list of web shops that were targeting IE first because "more advanced" and complaining about other browsers because they "suck". And it looked wrong to just about everyone else who targeted other browsers because Microsoft. Now, we've a laundry list of web shops that are targeting Chrome first because "more advanced" and complaining about other browsers because they "suck". And for some reason those browsers should all catch-up and fast because Google?
- zghst 9y ago
  amen
- pmontra 9y ago
  If Safari would run on Windows and Linux maybe everybody would develop with it and take advantage of this least common denominator thing (but still wish it would get on par with the other browsers.) Unfortunately it is not. This app store first / web second policy served well Apple bottom line. Too bad web developers are paying for it with extra work and this is the point of the post.

by n42 9y ago

That is because Safari's feature support is the lowest common denominator of the other browsers. By developing on it you are ensuring you don't use features every other browser but Safari supports.

protobuflol 9y ago

Unless of course you're referring to ES6 support, in which case it has the best support.

n42 9y ago
You're probably right, I only have to deal with CSS inconsistencies since JS tooling largely solves that problem for me these days. Unfortunately tools like CSS prefixer can't solve for everything.
- protobuflol 9y ago
  Totally. Anecdotally, though, a) firefox diverges further from chrome than safari does and b) the types of CSS flaws don't wven approach the black magic of designing for IE6.

ddebernardy 9y ago

> By developing on it you are ensuring you don't use features every other browser but Sure. But isn't developing against the least common denominator precisely what web development has been all about in the past 20 years or so? Edit: Just to expand on that... Then, there was a laundry list of web shops that were targeting IE first because "more advanced" and complaining about other browsers because they "suck". And it looked wrong to just about everyone else who targeted other browsers because Microsoft. Now, we've a laundry list of web shops that are targeting Chrome first because "more advanced" and complaining about other browsers because they "suck". And for some reason those browsers should all catch-up and fast because Google?

zghst 9y ago
amen
pmontra 9y ago
If Safari would run on Windows and Linux maybe everybody would develop with it and take advantage of this least common denominator thing (but still wish it would get on par with the other browsers.) Unfortunately it is not. This app store first / web second policy served well Apple bottom line. Too bad web developers are paying for it with extra work and this is the point of the post.