Hacker News Reader

Full thread

lyschoening

We're at ECMAScript 2017 now. The author is one version behind.

View on HN

ES2017 is also a much more consequential revision:

* async functions

* shared buffers (between workers) and atomic operations for these buffers

* additional native object methods (Object.values, Object.entries, Object.getOwnPropertyDescriptor, string padding)

* trailing commas in function argument lists (definition & callsite)

* unicode case folding in /ui

When's the `|>` pipe operator expected?

That… doesn't even make sense as a question.

All one can say about it is that it was promoted to Stage 1 18 days ago, that the spec is not currently written, and that it has two dozen issues opened against it.

JavaScript,where even the "newest version" is already outdated

The committee is now using yearly releases, so the "newest version" is outdated every year in June. The 7th edition is ES2016, and was superseded by the 8th edition (ES2017) finalised in June 2017.

I think it would be a bit more "correct" to say that each spec is outdated as soon as it is cut :) At least no one in the committee considers the last released spec "current" -- they prefer everyone point to the github repo.

Reply on news.ycombinator.com