3 ms·
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.
by scotth 13y ago
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.
- kevingadd 13y agoThis 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.
- pornel 13y agoHopefully improvements like this shipping now will pressure other vendors to catch up. Apart from Apple all major players have short release cycles and automatic updates now, so maybe it won't be that bad.