5 ms·

Safari is the new IE6, stop supporting it and let it die. It will not get any better anyway. If most of your users are on iOS, then make an app for them, it's w

by olavgg 10y ago

Safari is the new IE6, stop supporting it and let it die. It will not get any better anyway. If most of your users are on iOS, then make an app for them, it's what Apple also want you to do...

drinchev 10y ago
I switched from Chrome to Safari 5 months ago. The memory usage in Safari is far more superior than Chrome / Firefox on OS X. Also the CPU usage is relatively low, which means more time on battery for me. I still use Chrome for development, though. Safari, is not as bad as IE6 was and anyway no professional front-end developer would make a website that is not working properly on iOS Safari, so it's kinda obvious it will stay supported for a long, long time. So I would consider what the OP is doing with the CSS, something that might also work on Safari, but with some polyfills.
Yaggo 10y ago
Oh please. Safari 10 (both desktop & iOS versions) is the only browser with 100% ES6 compatibility. All browsers have some issues (e.g. Chrome still does not support 'sticky' position, Safari hasn't implemented Service Workers, etc), that's part of the multi-vendor / open-standard game. http://kangax.github.io/compat-table/es6/ http://kangax.github.io/compat-table/es6/
- Yaggo 10y ago
  Safari does have longer release cycle than e.g. Chrome, because Apple provides very uniform / polished support for wide range of devices (Macs, iOS devices, including very old ones such as iPhone 4S).
mozumder 10y ago
I have no idea why people use Chrome. Chrome/Google has terrible/no support of many browser layout & interaction features, such as CSS Regions & scroll snap points. Also, Safari is just a much better browser than Chrome. We need to make sure people stop using Chrome and move to the default browser in their environment - Safari & Edge. If you support the default browser, then you're going to be fine.
- pluma 10y ago
  > default browser Hi, I'm Linux.
  - pmlnr 10y ago
    Yay for Midori, Konqueror, Epiphany, Dillo, lynx, and all the things a regular dev never have to encounter with :) ( By the way lynx is perfect to pierce through a lot of paywalls. )
    - pluma 10y ago
      Chrome is still the best choice for development on Linux. The alternatives are Opera and Firefox. Everything else is like coding while wearing mittens.
- Lio 10y ago
  Well I use Chrome because I find the development tools to be much better than those in Safari. It gets tedious switching the default browser setting over so I tend to just use Chrome for everything.
coldtea 10y ago
>Safari is the new IE6, stop supporting it and let it die. Not sure what old wives tales you have heard, but actually Safari was the first browser to 100% support ES6. And compared to Chrome, it uses 1/3 less battery...
- arkx 10y ago
  He is parroting a year old clickbait headline (https://nolanlawson.com/2015/06/30/safari-is-the-new-ie/ https://nolanlawson.com/2015/06/30/safari-is-the-new-ie/) where the main gripes were that - Apple didn't attend EdgeConf 2015 - https://webkit.org/blog/ https://webkit.org/blog/ was not updated often enough - Safari 9 had a seriously buggy IndexedDB (fixed in Safari 10)
  - olavgg 10y ago
    I would rather refer to this https://news.ycombinator.com/item?id=12051267 https://news.ycombinator.com/item?id=12051267 I'm not the only one who think Safari is a joke compared to the competition. While IE6 was much much worse than what Safari is today, I feel like history is repeating itself again. And ES6 support is irrelevant when the main goal is to make sure websites renders and behave correctly, which is more painful for Safari than the other browsers. I still have flexbox issues on Safari https://bugs.webkit.org/show_bug.cgi?id=136041 https://bugs.webkit.org/show_bug.cgi?id=136041
    - coldtea 10y ago
      >I'm not the only one who think Safari is a joke compared to the competition. How does that opinion survive reality, e.g. Safari being the first browser to reach 100% ES6 compliance? >I still have flexbox issues on Safari https://bugs.webkit.org/show_bug.cgi?id=136041* https://bugs.webkit.org/show_bug.cgi?id=136041* So? All browsers still have Flexbox issues. Here are Chrome's: https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3ABlink%3ELayout%3EFlexbox+&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids https://bugs.chromium.org/p/chromium/issues/list?can=2&q=com...
fredsir 10y ago
Websites and browsing it self look and feel smoother in Safari compared to Google Chrome. Font rendering in Safari feel like font rendering in the rest of macOS. Not always but sometimes the same website has proper fonts in Safari but looks awkward in Chrome for some reason, I dunno why. Safari has proper GUI (especially settings) that feels at home in macOS instead of some weird web-based settings. Safari uses so much less power for the same usage compared to Chrome. It's just my anecdotal view, but I believe that Chrome might be better for developers, but websites are made for the users, not the developers, and Safari is far superior on that front.
glenndebacker 10y ago
"Safari is the new IE6, stop supporting it and let it die." I can only assume you never went through the pain that IE6 delivered... It has been some years now but I still get nightmares about it. It literally made me question at one time if I didn't made the wrong choice to focus on web development. Apple may be dragging its feet when adapting new api stuff, but the situation is by no means comparable as what the situation was with IE6. Not by a million miles.
- mcbits 10y ago
  IE6 wasn't so bad. It could do everything in 2001 that practically every site needs today, and pretty intuitively if you didn't also support other browsers. But dealing with emerging "standards compliant" browser bugs alongside "the de facto standard" IE6 bugs in the same code, and eschewing table layout before CSS was up to the task, that was a nightmare.

by olavgg 10y ago

Safari is the new IE6, stop supporting it and let it die. It will not get any better anyway. If most of your users are on iOS, then make an app for them, it's what Apple also want you to do...

drinchev 10y ago

I switched from Chrome to Safari 5 months ago. The memory usage in Safari is far more superior than Chrome / Firefox on OS X. Also the CPU usage is relatively low, which means more time on battery for me. I still use Chrome for development, though. Safari, is not as bad as IE6 was and anyway no professional front-end developer would make a website that is not working properly on iOS Safari, so it's kinda obvious it will stay supported for a long, long time. So I would consider what the OP is doing with the CSS, something that might also work on Safari, but with some polyfills.

Yaggo 10y ago

Oh please. Safari 10 (both desktop & iOS versions) is the only browser with 100% ES6 compatibility. All browsers have some issues (e.g. Chrome still does not support 'sticky' position, Safari hasn't implemented Service Workers, etc), that's part of the multi-vendor / open-standard game. http://kangax.github.io/compat-table/es6/ http://kangax.github.io/compat-table/es6/

Yaggo 10y ago
Safari does have longer release cycle than e.g. Chrome, because Apple provides very uniform / polished support for wide range of devices (Macs, iOS devices, including very old ones such as iPhone 4S).

mozumder 10y ago

I have no idea why people use Chrome. Chrome/Google has terrible/no support of many browser layout & interaction features, such as CSS Regions & scroll snap points. Also, Safari is just a much better browser than Chrome. We need to make sure people stop using Chrome and move to the default browser in their environment - Safari & Edge. If you support the default browser, then you're going to be fine.

pluma 10y ago
> default browser Hi, I'm Linux.
- pmlnr 10y ago
  Yay for Midori, Konqueror, Epiphany, Dillo, lynx, and all the things a regular dev never have to encounter with :) ( By the way lynx is perfect to pierce through a lot of paywalls. )
  - pluma 10y ago
    Chrome is still the best choice for development on Linux. The alternatives are Opera and Firefox. Everything else is like coding while wearing mittens.
Lio 10y ago
Well I use Chrome because I find the development tools to be much better than those in Safari. It gets tedious switching the default browser setting over so I tend to just use Chrome for everything.

coldtea 10y ago

>Safari is the new IE6, stop supporting it and let it die. Not sure what old wives tales you have heard, but actually Safari was the first browser to 100% support ES6. And compared to Chrome, it uses 1/3 less battery...

arkx 10y ago
He is parroting a year old clickbait headline (https://nolanlawson.com/2015/06/30/safari-is-the-new-ie/ https://nolanlawson.com/2015/06/30/safari-is-the-new-ie/) where the main gripes were that - Apple didn't attend EdgeConf 2015 - https://webkit.org/blog/ https://webkit.org/blog/ was not updated often enough - Safari 9 had a seriously buggy IndexedDB (fixed in Safari 10)
- olavgg 10y ago
  I would rather refer to this https://news.ycombinator.com/item?id=12051267 https://news.ycombinator.com/item?id=12051267 I'm not the only one who think Safari is a joke compared to the competition. While IE6 was much much worse than what Safari is today, I feel like history is repeating itself again. And ES6 support is irrelevant when the main goal is to make sure websites renders and behave correctly, which is more painful for Safari than the other browsers. I still have flexbox issues on Safari https://bugs.webkit.org/show_bug.cgi?id=136041 https://bugs.webkit.org/show_bug.cgi?id=136041
  - coldtea 10y ago
    >I'm not the only one who think Safari is a joke compared to the competition. How does that opinion survive reality, e.g. Safari being the first browser to reach 100% ES6 compliance? >I still have flexbox issues on Safari https://bugs.webkit.org/show_bug.cgi?id=136041* https://bugs.webkit.org/show_bug.cgi?id=136041* So? All browsers still have Flexbox issues. Here are Chrome's: https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3ABlink%3ELayout%3EFlexbox+&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids https://bugs.chromium.org/p/chromium/issues/list?can=2&q=com...

fredsir 10y ago

Websites and browsing it self look and feel smoother in Safari compared to Google Chrome. Font rendering in Safari feel like font rendering in the rest of macOS. Not always but sometimes the same website has proper fonts in Safari but looks awkward in Chrome for some reason, I dunno why. Safari has proper GUI (especially settings) that feels at home in macOS instead of some weird web-based settings. Safari uses so much less power for the same usage compared to Chrome. It's just my anecdotal view, but I believe that Chrome might be better for developers, but websites are made for the users, not the developers, and Safari is far superior on that front.

glenndebacker 10y ago

"Safari is the new IE6, stop supporting it and let it die." I can only assume you never went through the pain that IE6 delivered... It has been some years now but I still get nightmares about it. It literally made me question at one time if I didn't made the wrong choice to focus on web development. Apple may be dragging its feet when adapting new api stuff, but the situation is by no means comparable as what the situation was with IE6. Not by a million miles.

mcbits 10y ago
IE6 wasn't so bad. It could do everything in 2001 that practically every site needs today, and pretty intuitively if you didn't also support other browsers. But dealing with emerging "standards compliant" browser bugs alongside "the de facto standard" IE6 bugs in the same code, and eschewing table layout before CSS was up to the task, that was a nightmare.