Benjamin Gruenbaum
Benjamin Gruenbaum
> Look, you should not trust benchmarks that use scores in this way anyway, You really confused me here... First, the Node.js benchmarks let you plot the results - fon...
@JobLeonard I'll clarify, when I say the Node benchmarks I meant running this tool and not benchmark.js: https://github.com/nodejs/node/tree/master/benchmark
@JobLeonard this is an internal tool we use at Node, I recommended it since it's the only benchmarking tool for JS that I know and is reasonable - sorry for...
Hey - are there any updates on this proposal? When do you expect to present it again? (I am asking because Node.js has started to integrate async iterators in many...
@karlhorky - Every stream is async iterable (so you can for `await (const chunk of createReadStream('file')`), and http requests are async iterable). - Events are async iterable with `on` (`on(emitter,...
And to clarify - I think it's safe to say Node.js is _very_ interested in this proposal and since a bunch of our use cases arose from web platform APIs...
@Jack-Works I believe the whole point of “for await of” with async iterators is to serialize code so it appears sync yet works with backpressure (not requesting more items from...
That’s great thanks for the update :)
@ussjoin 👋 First of all thank you for engaging, championing this change and starting to do the technical work in that PR. I think there are some misconceptions, I am...
@artsyca Edit: hiding as the comment has been removed. Hey. If you are bothered by this and are open to convincing other people of the importance of renaming JS in...