News for hackers. Stuff that matters.

A comment on JSC loves ES6. Parent comment

Re:JSC loves ES6 by smitherfield on Monday June 05, 2017 @06:28PM (#14492831)
Although IIRC Chrome and/or Firefox had all but guaranteed tail-call optimization (not a source code-level feature, obviously) first.
[ Parent | on HN ]
Re:JSC loves ES6 by pizlonator on Monday June 05, 2017 @06:39PM (#14492924)
I don’t think that’s right. Source?
[ Parent | on HN ]
Re:JSC loves ES6 by smitherfield on Monday June 05, 2017 @07:39PM (#14493352)
Just Chrome, but yes: http://web.archive.org/web/20160303192336/http://kangax.gith...
[ Parent | on HN ]
Re:JSC loves ES6 by pizlonator on Monday June 05, 2017 @08:07PM (#14493554)
That shows WebKit supporting tailcalls. It doesn’t a show Chrome supporting tail calls.

I vividly remember us implementing tail calls and v8 not having them yet at that time. This was almost 2 years ago.

[ Parent | on HN ]
Re:JSC loves ES6 by justabystander on Monday June 05, 2017 @09:11PM (#14493926)
Chrome has had them for a while. Supposedly they just hid them behind a flag because they weren't satisfied with some perceived deficiencies in the spec. (Check out https://v8project.blogspot.com/2016/04/es6-es7-and-beyond.ht...) WebKit did have it somewhere between mid-October to early December of 2015. (http://web.archive.org/web/20151207203829/http://kangax.gith...) Chrome didn't get it until late April of the next year (http://web.archive.org/web/20160526102037/http://kangax.gith...), though there's no snapshot until late May. People worked on the spec in a different order.

Chrome also had a failing array prototype under some non-standard syntax for a while. Despite claiming 100%, Kangax didn't show them passing. Test results have fluctuated as the tests themselves were refined. I've seen some passing results later turn into fails. That's why none of the browsers are at 100% for ES6 currently.

I'm still grudging at Apple for the year's delay between Safari 9 and 10, which left all the clueless Apple customers on ~53% ES6. Yes, WebKit had regular updates, but they didn't do a gradual release and few people thought to install WebKit instead of Safari (or even the TP). Other browsers had much better beta channels than Apple. And didn't pointlessly delay on things like WebRTC. Or block other browser engines like iOS to protect their app store.

Chrome did a good job of releasing updates gradually, but there are still some ES6 performance issues to be ironed out.

[ Parent | on HN ]
Re:JSC loves ES6 by alwillis on Tuesday June 06, 2017 @01:15AM (#14494903)
I'm still grudging at Apple for the year's delay between Safari 9 and 10, which left all the clueless Apple customers on ~53% ES6.

But Apple got to 100% ES6 support before anyone else: https://twitter.com/webkit/status/728643624464883712?lang=en

[ Parent | on HN ]
Re:JSC loves ES6 by pjmlp on Tuesday June 06, 2017 @03:57AM (#14495529)
We still need to target things like IE 9 or older FF ESR releases, so Safari current status is already pretty advanced.
[ Parent | on HN ]
Re:JSC loves ES6 by smitherfield on Monday June 05, 2017 @08:09PM (#14493566)
That's what I said.
[ Parent | on HN ]
Re:JSC loves ES6 by pizlonator on Monday June 05, 2017 @08:12PM (#14493590)
Chrome and WebKit are two different things. So, no, you didn’t just say that.
[ Parent | on HN ]
Re:JSC loves ES6 by deecewan on Monday June 05, 2017 @08:42PM (#14493773)
He said that chrome and Firefox had everything except for tail call optimisation earlier.
[ Parent | on HN ]
Re:JSC loves ES6 by pizlonator on Monday June 05, 2017 @08:57PM (#14493856)
Ha! I read your comment as: Chrome had tail calls first, but they were all but guaranteed. I was confused, but once I parsed your sentence that way there was no going back.

I am now in agreement with everything you said. Thanks for clarifying.

[ Parent | on HN ]
Re:JSC loves ES6 by saamyjoon on Tuesday June 06, 2017 @01:17AM (#14494912)
FWIW, I don’t think this is accurate (not that it really matters much anymore). All the browsers were in the 90+% support around the same time.
[ Parent | on HN ]