billti / node-es2015 Goto Github PK

In the proposal it states that

... there is no value but much complexity in also including an ES2015 version...

It is important for the discussion that value is use in the objective meaning: i.e.: It doesn't yield any benefit compared to other variants. The use here seems to be "its value is diminishable" or "compared to the other solution the value is not worth mentioning". I noticed upon that because for many people there is important value in it!

1. If a person wants her open-source project to switch to ES2015 modules she expects that people write PR's etc. as ES2015 modules but just because she prefers ES2015 modules doesn't mean that she doesn't care about people who use old versions of Node.js. NPM supports node to 0.8 or so... for reference...
2. If one package is stripped from the possibility to contain multiple dialects, the user-land will create packages like async-es2015 or async-legacy which shifts this discussion from here to npm and will cause an even more problematic feature/shift and fragmentation of the community. (how many -es2015 variant packages will the be in npm?)

The README was copied from an earlier Gist, and should be updated to reflect the latest info from discussions with @jdalton around unambiguous grammar and repeat parse attempts.

@jdalton The info in https://github.com/billti/node-es2015/blob/master/algorithms.md file is up to date, and much of the README is as discussed (esp. with regards to why not to do fat packages with side-by-side versions of the same module). Please take a look, and loop in @bmeck if desired.

Pinging @ahejlsberg to check the algorithms write-up (especially the hoisting) is per our chat earlier.