ES2016+

[graingert]

No description provided.

[bcoe]

@graingert I'm happy with this, by consistently also using the term Babel (which is taking on meaning) I think we'll help eliminate confusion.

I wish there was a better catch-all term than ES2015/ES2016/ES6/ES6/etc. though.

[graingert]

I've been using

`ES${currentYear}+`

[MoOx]

Some idea: ESx, ES*, ES+, ESn+1. ES+ seems correct and understandable for me.

[kentcdodds]

should be ES2015+

[bcoe]

@kentcdodds @graingert I myself am confused by what the appropriate naming should be for ES6 at this point. The important thing, given that this is for documentation, is that we minimize the surprise of the community. Here's what I think:

1. it's more important that we pull together an elegant set of examples, and documentation for the website.
2. we use whatever terminology Babel is currently using, and update our terminology accordingly. Looking at https://babeljs.io/, I'm in agreement with @kentcdodds that for the time being we use the term ES2015+. I also see that they're moving towards the phrase "next generation JavaScript".

To reiterate, the important thing is that newcomers aren't confused by our documentation (this is much more important than being correct). @kentcdodds what terminology have you been using when teaching people?

[graingert]

Argh you said ES6!

On 3 Aug 2016 21:27, "Benjamin E. Coe" [email protected] wrote:

@kentcdodds https://github.com/kentcdodds @graingert
https://github.com/graingert I myself am confused by what the
appropriate naming should be for ES6 at this point. The important thing,
given that this is for documentation, is that we minimize the surprise of
the community. Here's what I think:

1. it's more important that we pull together an elegant set of
   examples, and documentation for the website.
2. we use whatever terminology Babel is currently using, and update
   our terminology accordingly. Looking at https://babeljs.io/, I'm in
   agreement with @kentcdodds https://github.com/kentcdodds that for
   the time being we use the term ES2015+. I also see that they're moving
   towards the phrase "next generation JavaScript".

To reiterate, the important thing is that newcomers aren't confused by our
documentation (this is much more important than being correct).
@kentcdodds https://github.com/kentcdodds what terminology have you
been using when teaching people?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#10 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZQTIhjzZaXUu8nyFt_Db1J4jQlPWXbks5qcPmfgaJpZM4Jb-yd
.

[kentcdodds]

I use the term ES6. I'd say that if someone knows what ES2015 is, they know what ES6 is. But it's not always true that someone who knows what ES6 is will know that ES2015 is the "official" name for the spec.

Many trainings, tutorials, etc. use "ES6" to refer to ES2015.

But I'm fine with saying ES2015+. But I don't see any reason to leave off ES2015 altogether...

[bcoe]

I'm coming around to Babel + ES6/ES2015 -- @graingert I totally hear your argument that this isn't technically correct, and it would be good to move towards a consistent naming convention as a community, but I don't want people to have trouble finding docs because they're not knowledgeable of insider baseball.

@hzoo would love to know your thoughts, coming from the Babel community ... just mainly curious at this point.

[hzoo]

Personally I'm ok with ES6 like @kentcdodds mentions - that's just what people say most of the time. It makes sense as the first version that switched to yearly naming