Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Safari Technology Preview supports 100% of the ES2015/16/17 features

kangax.github.io

Post reply on HN
Print view View original

111–120 of 126 posts

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#111

Post by vbezhenar »

ggregoire wrote: post #5

Honnest question for Safari users: why Safari? I don't really know Safari. I used Chrome on Windows and iOS, and when I moved to OSX I naturally continued with Chrome. And the dev tools are really great.

For me Safari works good enough, so I don't have many reasons to switch. Chrome development tools are marginally better, so it's still installed and I use it for some heavy JavaScript development, but outside of this I prefer Safari.

Funny enough, I had to use Windows 10 for a short time, and Edge was actually not that bad. I remember IE being the terrible product and everyone used some other browser. Now Edge is usable and there's no much reason to install Chrome there as well.

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#112

Post by ClassyJacket »

WhitneyLand wrote: post #90
Alex3917 wrote: post #47

Earlier quoted context omitted.

The power efficiency isn't even close. The 2016 MBP battery lasts about 10 hours running Safari versus 3 hours running Chrome. I've never particularly liked Safari, but I'm close to switching myself because Chrome is such a disaster. From the energy impact tab on the Activity Monitor: Chrome: 43 Safari: 0.3

10 hours vs 3 hours for current browser versions, running equivalent tabs/extensions/settings? Sorry but I don't believe you. Can you point to battery benchmarks or is this an off the cuff personal test? Are you talking about an old version of Chrome? You're aware they've been making progress recently? https://9to5mac.com/2016/09/06/google-chrome-mac-battery-per...

On my preview MBP it was about half. 6 hours on Safari meant I got 3 hours on Chrome.

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#113

Post by Rebelgecko »

kibibu wrote: post #80
Alex3917 wrote: post #47

Earlier quoted context omitted.

The power efficiency isn't even close. The 2016 MBP battery lasts about 10 hours running Safari versus 3 hours running Chrome. I've never particularly liked Safari, but I'm close to switching myself because Chrome is such a disaster. From the energy impact tab on the Activity Monitor: Chrome: 43 Safari: 0.3

Yeah, Safari kills all JavaScript threads - even on active tabs - after 90 seconds or so.

I haven't checked this recently, but in the past Chrome always turned on the dedicated GPU on my MBP, whereas Safari ran just fine with the integrated one.

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#114

Post by cgvgffyv »

WhitneyLand wrote: post #102
enraged_camel wrote: post #99

Earlier quoted context omitted.

>>10 hours vs 3 hours for current browser versions, running equivalent tabs/extensions/settings? Sorry but I don't believe you. My experience is the same. I have a 2011 MBA. With Safari, the battery lasts 4 hours. With Chrome, about 90 minutes. My browsing habits are the same between browsers.

Are you aware of the recent improvements in Chrome 53 energy use? Are your numbers before or after this? What was your test methodology, or was this ad-hoc? If there were reliable sources reporting similar numbers it would be easier to swallow, but I can't find a single source that claims it's this bad.

Spotted the Chrome dev.

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#115

Post by witty_username »

barumrho wrote: post #14
ggregoire wrote: post #5

Honnest question for Safari users: why Safari? I don't really know Safari. I used Chrome on Windows and iOS, and when I moved to OSX I naturally continued with Chrome. And the dev tools are really great.

(Not sure how to format this) - Battery life - Bookmark syncing and continuity (opening tabs from any of your other devices) - Content blocker API (so that ad blocker extension doesn't see all of the content) - Not having browsing history sent to Google I use Chrome for Flash content and Facebook.

I have not heard of Chrome sending browser history without my consent. Source?

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#116

Post by chipotle_coyote »

cmod wrote: post #103
eridius wrote: post #16

Earlier quoted context omitted.

Many reasons. Among those I care about: * It's a lot more power-efficient than any other browser. * In my experience, it's often faster than Chrome. * It follows platform conventions. I still get weirded out by Chrome cramming everything into that ⋮ button. * It syncs history, favorites, and open tabs over iCloud to Safari on my phone. It also supports Handoff. * It's not made by Google, a company that I prefer to gi…

And on the typography front: * Properly hyphenates

I've been (mildly) irritated for years that Chrome's devs have taken so long to put in CSS hyphenation support; this has been supported in other browsers since ~2012. It looks like it's finally got partial support since Chrome 55, although caniuse.com says it's still Mac-only.

https://bugs.chromium.org/p/chromium/issues/detail?id=605840

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#117

Post by yusukesuzuki »

nfriedly wrote: post #62

Does it support JS Modules? (I don't think the kangax compatibility table has a test for that, but the last time I looked, no browser supported it yet.)

The compat table does not include the modules (See the rationale here[1]). But STP19 supports the modules.

[1]: https://github.com/kangax/compat-table/issues/316#issuecomme...

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#118

Post by DavideNL »

ggregoire wrote: post #5

Honnest question for Safari users: why Safari? I don't really know Safari. I used Chrome on Windows and iOS, and when I moved to OSX I naturally continued with Chrome. And the dev tools are really great.

i also use Safari on my Macbook;

Firefox sucks because it still doesn't support the smooth "pinch to zoom", which Safari and Chromium have had for years. To me zooming seems such a basic functionality which is used so often, it feels like driving a car without rear mirrors or something...

Chromium/Chrome = Google, which i avoid due to lack of privacy.

One of the things i dislike in Safari is the lack of many extensions/addons which Chromium/Firefox do have. I wonder why this functionality is missing ?

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#119

Post by Oletros »

barumrho wrote: post #14
ggregoire wrote: post #5

Honnest question for Safari users: why Safari? I don't really know Safari. I used Chrome on Windows and iOS, and when I moved to OSX I naturally continued with Chrome. And the dev tools are really great.

(Not sure how to format this) - Battery life - Bookmark syncing and continuity (opening tabs from any of your other devices) - Content blocker API (so that ad blocker extension doesn't see all of the content) - Not having browsing history sent to Google I use Chrome for Flash content and Facebook.

> - Bookmark syncing and continuity (opening tabs from any of your other devices)

Is it not the same with Chrome?

Re: Safari Technology Preview supports 100% of the ES2015/16/17 features

#120

Post by dragonwriter »

MBCook wrote: post #93
dragonwriter wrote: post #78

Earlier quoted context omitted.

> This is because Google/YouTube is pushing VP9 streams when they detect that you're using Chrome. It saves them few megs on bandwidth (over H.264) but you suffer for it because VP9 is not hardware accelerated VP9 can be hardware accelerated, and AFAIK current Chrome supports hardware acceleration for VP9 with hardware that supports it.

Are there any normal desktops/laptops that support it? I'd be amazed if anything other than Chromebooks and Android had it.

> Are there any normal desktops/laptops that support it?

From what I've been able to find:

NVidia Pascal has full hardware decoding for VP9, as does the NVidia GM206.

And Intel's (now shipping, but not in consumer hands yet until probably next month, IIRC) Kaby Lake has full hardware decoding support, too.

(A lot more existing GPUs have hybrid support, but that's still got a CPU cost.)

Post reply on HN