3 ms·
You made a similar comment elsewhere about ES6 being "half-baked", and I'll ask my question again here: Can you explain more what is half-baked about ES6 modul
by an1sotropy 4y ago
You made a similar comment elsewhere about ES6 being "half-baked", and I'll ask my question again here:
Can you explain more what is half-baked about ES6 modules? To me the logic and syntax of how imports [1] and exports [2] are organized seems clean, but maybe I'm missing something?
[1] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
[2] https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/export https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
- MCArth 4y agoI agree, if we had all started with it, it is nice. But it completely breaks backwards compatibility with the whole existing node.js ecosystem, costing countless developer hours. It seems very likely to me a solution could have been found that would allow node to support the combination of esm and cjs.
- an1sotropy 4y agook, that makes sense (and sorry for making you answer twice). But I think sometimes a clean break is a necessary part of progress.