4 ms·
I believe I followed that, until that last paragraph. Are you implying that IO.js wasn't javascript?
by ep103 9y ago
I believe I followed that, until that last paragraph. Are you implying that IO.js wasn't javascript?
- erikpukinskis 9y agoNo, it's ES6. Class hierarchies, promises, etc, were liberately left out of JavaScript. ES6 is something, but it's not JavaScript. Sadly the brand was hijacked.
- ep103 9y agothat'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.