This is all well and good, but am I correct in saying that we won't be able to use native arrow functions for years. It's kind of tough to be excited about.
This is true for pretty much every ES6 feature - lots of them have shipping implementations in Firefox and/or Chrome, but they've all been hidden behind preferences for years, or are slightly out of sync with the spec, or are half-implemented, etc... Notable examples are Map, Set, and WeakMap, all of which have been behind a Chrome preference for years. In particular the lack of WeakMap makes entire classes of applications much harder to implement in Chrome than Firefox.
Ok the draft calls it "arrow function" (how fat arrows are used). I'm talking about how is (some) languages, "=>" is referred as "fat arrow" or "right arrow" as opposed to "->" thin arrow.
9 comments
[ 2.9 ms ] story [ 36.7 ms ] threadApart from Apple all major players have short release cycles and automatic updates now, so maybe it won't be that bad.
edit: since I get downvoted, source : https://www.google.com/#q=fat+arrow+es6
I mean, I don't invent anything :
https://bugzilla.mozilla.org/show_bug.cgi?id=979923
https://www.google.com/search?sitesearch=bugzilla.mozilla.or...
If they aren't called fat arrow, then the title is good.
The site's maintainer, kangax, on Firefox's recent ES6 work: https://twitter.com/kangax/status/456219547968614400