3 ms·
Can someone explain what this means for the browser ecosystem? What are the next steps to integration?
by rememberlenny 11y ago
Can someone explain what this means for the browser ecosystem? What are the next steps to integration?
- notNow 11y agoIt's underway already. Check out Kangax's amazing work here [0] [0] ES6 COMPAT TABLE: https://kangax.github.io/compat-table/es6/ https://kangax.github.io/compat-table/es6/
- bobajeff 11y agoI think it means we can now pine over EcmaScript 7.
- mrspeaker 11y agoDon't pine, just use Babel ;) http://kangax.github.io/compat-table/es7/ http://kangax.github.io/compat-table/es7/
- _greim_ 11y agoDepending on the browser, lots of things are already implemented, either generally available (e.g. `Promise`) or behind flags (e.g. fat arrows). This announcement just accelerates the adoption pipeline by reducing worry about spec changes.