Re:ES6, ES7, and beyond
by grifter2000 on Friday April 29, 2016 @05:57PM
(#11599034)
PLEASE don't do the awkward .mjs thing. I and prob most devs will simply not respect it.
[ Parent
| on HN ]
That's up to the Node.js team, not the V8 team, right?
But yes, Node.js team, please don't inflict .mjs on us, or let your extreme NIH block the introduction of ES2015 modules.
Re:ES6, ES7, and beyond
by grifter2000 on Friday April 29, 2016 @07:36PM
(#11599436)
Right, thank you
https://github.com/dherman/defense-of-dot-js/blob/master/pro...
Though there may need to be some considerations for `exports`/`module.exports` vs the `export` directive.
.es sounds good to me.
Seems like a good fit for EcmaScript. It might even help finally renaming the language, so that tech recruiters confuse it with something else ;)
> so that tech recruiters confuse it with something else
At least if a recruiter starts asking you about your Eczema experience, you can more easily determine that the screening process has gone off the rails.
That would be incorrect though, there are other implementations of the ES specification that are not JavaScript (UnityScript for example).
Although it's a cute suggestion.
WAT? UnityScript is not an implementation of ES AFAICT. It's entirely made up by Unity and has almost nothing in common with JavaScript/EMCAScript
.js, .jsx, .mjs, what's next? .js8?
Exactly why we should avoid more extensions. I don't see what's wrong with a config, either package.json or System.global