-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Summit Topic: Streams Future API(s) Session #82
Comments
I would love to attend in order to understand it better as well as understand why the API change is needed for the performance improvements (and why?). I would also appreciate any slides you have on the topic (or if you've given a talk about it - that would also help). |
Can we add this to the "Future of Streams" Discussion? We will talk about nodejs/node#20096 cc @mafintosh. |
Unfortunately, I don't have any slides. (I'm on Vacation atm so also won't be making much of anything.) I think there should be enough collective knowledge between myself, James, and Matteo to be able to disseminate it better at the summit, though. |
I won't be at the summit but would love for there to be discussion on this |
I'd like to attend at this session. |
Topic: Streams Session at the Collaborator Summit 2018 Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/942530127 Or iPhone one-tap : |
Some of the notes from the sessions:
|
If some folks were interested, I'd be willing to lead a kind of thing at the collab summit about how to move forward with our future streams api project (and/or alternatives).
This could include some kind of review / discussion about it and other potential alternatives.
cc @jasnell, @mcollina, @mafintosh, @addaleax
The text was updated successfully, but these errors were encountered: