2 ms·
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 prefere
by kevingadd 13y ago
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.