Jest: Use ES6 over ES2015

[hramos]

Our docs use both terms, ES2015 and ES6. While ES2015 is technically correct, ES6 has emerged as the more popular term. To avoid confusing people, let's always use ES6 unless when referring to a particular thing (e.g. babel-preset-es2015).

[cpojer]

Hmm, I disagree with this. I'd prefer to use the technical term "ES2015". I'm also happy if it is called "ES2015 (previously ES6)" in the beginning.

How about we simply call it by feature-name, given that many features are still receiving new features?

Example: "ES classes" instead of "ES2015 classes" unless we are actually talking about the specific feature.

[pedrottimark]

Agree with both principles:

• refer to version as little as possible
• use year 2015 or 2016 instead of 6 or 7, because starting in 2017, the version is by year only

Also please avoid stage numbers for experimental features because they are a moving target

[hramos]

Hmm, es6 is by far more commonly used than es2015. See es6 vs es2015 (es6 is blue):

[cpojer]

@hramos you are right but should we go for popularity or for the correct technical terms? I'll leave it up to you, because I don't feel strongly. I'm simply pointing out that the official names are ES3, ES5, ES2015, ES2016 and ES2017 so I'd prefer to use that rather than colloquial names.

[hramos]

I feel strongly about sticking to one term, and I'm fine with using ES2015. One last argument pro-ES6, if I may: it's what we ended up using in both the React and React Native docs refresh, and using ES6 here as well would ensure we're being consistent across doc sites.

[cpojer]

consistency wins, let's go with ES6 then, if that's what we do on our other major open source projects :)

[kentaromiura]

I'd argue that that may create confusion because we include the es2015 preset, not the ES6 preset.
I guess ES6 is more dominant in the web since the name was decided at the very end at the standardization process so all discussion and blog posts were talking about ES6 at that time.
Let you guys decide but, as you probably can see from my comment, I' m against using ES6. #bikeshed

[hramos]

Another data point: our own docs recommend using a ES2015 Proxy but identity-obj-proxy refers to it as a ES6 proxy.

We know in this thread that the term can be interchangeable, but in the interest of making the docs more accessible to more users we should opt for the popular term.

[pedrottimark]

To y’all who improved the React docs: Thank you! Thank you!! Thank you!!!

[hramos]

@pedrottimark <3