I like a lot of the features in Earl Grey, but one feature that I feel is lacking is proper support for ES6 modules.
My intention is to write client-side browser applications. I know that I can use Webpack to bundle CommonJS files (and I do use Webpack), but ES6 modules have many advantages:
http://www.2ality.com/2014/09/es6-modules-final.html
The basic gist of it is that ES6 modules are static, which means better compile-time error checking, faster code execution, dead code elimination (e.g. Rollup and Webpack2), support for macros, and better support for cyclic dependencies.
I'm not sure exactly what changes will need to be made in Earl Grey to support ES6 modules, but I think it's something that needs to be thought about at some point, because ES6 modules are the future.
I like a lot of the features in Earl Grey, but one feature that I feel is lacking is proper support for ES6 modules.
My intention is to write client-side browser applications. I know that I can use Webpack to bundle CommonJS files (and I do use Webpack), but ES6 modules have many advantages:
http://www.2ality.com/2014/09/es6-modules-final.html
The basic gist of it is that ES6 modules are static, which means better compile-time error checking, faster code execution, dead code elimination (e.g. Rollup and Webpack2), support for macros, and better support for cyclic dependencies.
I'm not sure exactly what changes will need to be made in Earl Grey to support ES6 modules, but I think it's something that needs to be thought about at some point, because ES6 modules are the future.