Repository navigation
against es6 in documentation #431
Description
i don't know if it was decided/voted or not, but i am against es6 features in documentation or code examples.
the docs and examples should be as simple as possible, and now even the classic createServer example ('about' page) has const, arrow functions, and template strings.
before you could just say 'copy this example, see how easy it is to create a server in node?', now you also have to explain what all those special signs and characters are.
Activity
stevemao commentedon Dec 30, 2015
I believe these examples are in the docs of nodejs that support them. If you switch to an older version they shouldn't be there.
wonderdogone commentedon Dec 30, 2015
I think it's good to push ES6 unless it's a feature set that is outside of Node internally. For example some ES6 that needs to be transpiled by external tool like babel should not be in docs because then you have to explain that workflow.
stevemao commentedon Jan 1, 2016
I don't think this is necessary. We already have docs about features in es2015. If we add a link to all the pages that have es2015 code it would be too noisy. Not to mention that there are many people already using es2015 and a there are a lot of material about es2015 online.
Closing this now. @forgotPassword if you find anything that does not work against the corresponding node version out of the box please fire a bug :) thanks.
rvagg commentedon Jan 14, 2016
Thanks for the link @stevemao, I knew there was an issue in here about this recently that I couldn't find.
Folks in here, please see #467 for possible way forward. Only discussion at this stage.