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

WebKit is now 100% ES6 complete

twitter.com

Post reply on HN
Print view View original

21–30 of 119 posts

Re: WebKit is now 100% ES6 complete

#21

Post by jdcarr »

antjanus wrote: post #15
brokentone wrote: post #10

Earlier quoted context omitted.

From my limited anecdotal testing no. In fact it may be slower. This is a good view of this: https://kpdecker.github.io/six-speed/ However... the potential upside is size. Native code will usually be smaller, which for a web client is a win.

I'm having trouble reading the table, when it says 16x slower, is it saying the implementation is slower or the engine?

You might be missing the header row of the table listing various engines and their versions, and the little note that says "Performance of ES6 features relative to the ES5 baseline operations per second."

And I would assume that the baseline has been established on a per-engine basis.

Re: WebKit is now 100% ES6 complete

#24

Post by sotojuan »

liquidise wrote: post #17
joeblau wrote: post #13

Is anyone using Safari Technical Preview as their main Browser? I was hesitant to use it, but I've heard a few people say that it's stable.

I tried for about a week. My complaints with it were the same i have with base Safari, but TP specifically worked fine. No unique issues despite using it as dev platform and a consumer browser.

I wish Safari would have the same incognito mode as Chrome's. Currently, tabs in the same incognito window do not share sessions so you have to log in again on every new tab.

Re: WebKit is now 100% ES6 complete

#26

Post by nostrademons »

swang wrote: post #19

Webkit was probably one of the last major web engines to start integrating ES6 features, yet they have TCOs done. Anyone explain what's holding it up in Chrome/FF/Edge?

There's some debate over whether tailcalls should be explicit or implicit, and Chrome/FF/Edge are leaning towards the explicit side:

https://news.ycombinator.com/item?id=11563305

Re: WebKit is now 100% ES6 complete

#27

Post by paulirish »

swang wrote: post #19

Webkit was probably one of the last major web engines to start integrating ES6 features, yet they have TCOs done. Anyone explain what's holding it up in Chrome/FF/Edge?

There's been heavy discussion (especially recently) on the value of implicit TCO for developers. I believe all three V8/Chakra/Spidermonkey all found TCO regresses performance a bit. Additionally, it hampers debugging considerably as call stacks are completely twisted.

There's been a lot of active discussion between browser vendors and TC39 recently to sort out a path forward. All teams are excited about explicit TCO syntax, but there remains skepticism that implicit TCO is good for users or developers.

Re: WebKit is now 100% ES6 complete

#29

Post by bendyorke »

joeblau wrote: post #13

Is anyone using Safari Technical Preview as their main Browser? I was hesitant to use it, but I've heard a few people say that it's stable.

I've been using it for about a month now as my main browser, haven't had any issues with it. Any issue's I had in Safari 9 seem to have been fixed :)

Re: WebKit is now 100% ES6 complete

#30

Post by hochchristoph »

glhaynes wrote: post #8
hochchristoph wrote: post #4

Earlier quoted context omitted.

Probably at WWDC, between June 13 and June 17.

Likely in the developer previews that they release during WWDC then available to consumers in the fall.

I don't think that it will take this long. They pushed out Safari 9.1 this year, which saw pretty significant changes. I think they could release the things from the tech preview with a 9.2 release for El Cap, maybe a month from now (WWDC coincidently?)
Post reply on HN