10 ms·

> Not surprising, given Google's stance for other languages. No, the reason is that Mozilla just added lots of stuff way before it got into the ES specs. http

by ahoge 12y ago

> Not surprising, given Google's stance for other languages. No, the reason is that Mozilla just added lots of stuff way before it got into the ES specs. https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_in_JavaScript/1.7 https://developer.mozilla.org/en-US/docs/Web/JavaScript/New_... That's from October 2006. It includes things like let/const, generators, iterators, and destructuring assignment. For reference, ES5 was published in December 2009. So, it's kinda like applauding Microsoft for supporting text-overflow:ellipsis first. It's something they added with IE6. It became part of the standards much later with CSS3.

gsnedders 12y ago
To be fair, quite a lot of these things have had to have relatively significant changes to match the ES6 spec.
masklinn 12y ago
> No, the reason is that Mozilla just added lots of stuff way before it got into the ES specs. That's only part of the reason, the linked page notes which features had been added by Mozilla (generally feature-gated). The count is 5 items of syntactic additions (out of 12), and 0 of standard library additions (out of ~40)
pjmlp 12y ago
> No, the reason is that Mozilla just added lots of stuff way before it got into the ES specs. No the reason is that adding Dart VM to Chrome is higher than JavaScript compliance. http://www.chromestatus.com/features http://www.chromestatus.com/features