Re:ECMAScript modules in Node.js: the new plan
by snek on Wednesday December 26, 2018 @10:50AM
(#18762695)
If you feel you can come up with a better solution for module syntax ambiguity please feel free.
Over the last three years we (including hundreds of devs like you who come in guns blazing calling us all idiots) haven't been able to come up with something that works better.
Re:ECMAScript modules in Node.js: the new plan
by ricardobeat on Wednesday December 26, 2018 @05:34PM
(#18765493)
That is a self-inflicted problem. Step away from the ambiguity by dropping cross-compatibility as everyone has been begging for.
Re:ECMAScript modules in Node.js: the new plan
by through on Wednesday December 26, 2018 @03:11PM
(#18764491)
Proposing or fixing a bug in a third party product should not affect a web standard. If you want my personal help to assist the NodeJS fix, yeah, I would be good there, but I can’t fix the toxic bikeshed culture that you obviously enjoy. MJS is NodeJS solution. It is not a web solution.
Re:ECMAScript modules in Node.js: the new plan
by through on Wednesday December 26, 2018 @03:16PM
(#18764516)
You could support .es file types which would work just as well and is more succinct than .mjs, but AFAIK the group won’t because of “branding” issues. Bull. Use .es. Standard semantics for ECMSScript which is the name of the language, no games or pretence.
Re:ECMAScript modules in Node.js: the new plan
by jdd on Thursday December 27, 2018 @10:43AM
(#18770089)
Node will likely end up with multiple ways to disambiguate modules. Until then, you might dig https://npmjs.com/esm. No .mjs required.
.mjs is an aberration, a solution to a poor implementation of one web server, not a solution. NodeJS need to do the hard work of solving their own problem and stop attempting to manufacture “real world solutions” with .mjs.