What is es6?
No dia Sexta-feira, 5 de Julho de 2013, gaglegagle...@gmail.com escreveu:
not yet
El martes, 2 de julio de 2013 17:41:16 UTC+2, Alan Gutierrez escribió:
Is it time to start using ES6 in Node.js libraries hosted on NPM? Or is
ES6
going to be the new CoffeeScript?
--
Alan
On Sunday, July 7, 2013, António Ramos wrote:
What is es6?
Ecma-262, v6 (ECMAScript)
Rick
No dia Sexta-feira, 5 de Julho de 2013,
gaglegagle...@gmail.comjavascript:_e({}, 'cvml',
'gaglegagle...@gmail.com');escreveu:
not yet
El martes, 2 de julio de 2013 17:41:16 UTC+2, Alan
Is it time to start using ES6 in Node.js libraries hosted on NPM? Or is ES6
going to be the new CoffeeScript?
--
Alan Gutierrez ~ @bigeasy
--
--
Job Board: http://jobs.nodejs.org/
Posting guidelines:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message
My rule is to not use anything that's behind a flag in libraries. But I do
use things like generators in my applications that consume libraries. I
also use generators in my examples and README's because it's so much
cleaner.
I've been using continuables heavily in place of callback-last APIs
Unless the ES6 spec for the feature is complete and implementation in v8 is
well tested it, at the least, won't be going into core. For example, callbacks
called through generators cannot be inlined. This leads to significant
performance degradation. As far as personal projects, feel free to
For ES6 features I apply the library / application line.
I avoid using something complex in library implementations, that includes
promises, generators, flow control, web frameworks. This is mainly to make
individual libraries as lean as possible, you can still use dependencies to
hide
