that's fair. But my understanding was the only reason JS !== to ES6, is because of deliberations and therefore lagging browser adoption. Its a relatively safe

that's fair. But my understanding was the only reason JS !== to ES6, is because of deliberations and therefore lagging browser adoption. Its a relatively safe bet that many ES6 features will be adopted. And those features that don't see adoption will likely eventually be dropped from node, eventually.