note: I’m using TypeScript to convert the async iterators and generators into something that node.js can run.
Isn’t it a bit of an unfair comparison? The author seems to be benchmarking a JavaScript implementation of async iterators and generators while pretending to benchmark a language feature. What they were actually running on node is this: https://gist.github.com/vhf/2b01fe4f867964a27fe617443ddf786b , presented as this: https://github.com/danvk/async-iteration/blob/master/async-iter.ts (I used this: https://www.typescriptlang.org/play/ )
I’d be more interested in an analysis running the actual language feature, I think it’s available on d8 (v8’s shell) via --harmony-async-iteration.
d8
--harmony-async-iteration
Wow. Really shot themselves in the foot with the spec they came up with.
Isn’t it a bit of an unfair comparison? The author seems to be benchmarking a JavaScript implementation of async iterators and generators while pretending to benchmark a language feature. What they were actually running on node is this: https://gist.github.com/vhf/2b01fe4f867964a27fe617443ddf786b , presented as this: https://github.com/danvk/async-iteration/blob/master/async-iter.ts (I used this: https://www.typescriptlang.org/play/ )
I’d be more interested in an analysis running the actual language feature, I think it’s available on
d8(v8’s shell) via--harmony-async-iteration.Wow. Really shot themselves in the foot with the spec they came up with.