.read() stream not fully explained

[davidgatti]

.read() stream not fully explained

[davidgatti]

Sure, but

• I need to refresh my memory why I created this issue, it was a while back
• I'll still need to understand the developer thinking to then take what info and convert it in to something anyone will be able to understand.

I'll be back 🕶

[davidgatti]

Anyone?

[sam-github]

Pipe because it supports back-pressure.

[davidgatti]

🤔 Hmm that answer assumes to much of me. If you had a longer moment could you write a little more to give a more clear explanation. I would be truly grateful.

[sam-github]

https://howtonode.org/streams-explained

I'm leaving this open, because it potentially indicates missing info in the docs, but this is not a place to ask for help understanding node, please use https://github.com/nodejs/help.

[davidgatti]

I think I know one or two things about stream ;) https://github.com/davidgatti/How-to-Understand-Streams-in-NodeJS. Anyway confusing documentation, no explanation given - o well, lets move on ;)

[sam-github]

@davidgatti I don't understand why you are asking questions about backpressure when you describe it here: https://github.com/davidgatti/How-to-Understand-Streams-in-NodeJS#the-best-use-case-of-a-stream-in-nodejs

Was it just to point out the docs don't describe it well?

Docs needs knowledgable contributors, please consider contributing your document as an initial "guide" to streams, or otherwise getting involved in the working group.

[sam-github]

Actually, I will close this as a duplicate of #25

[gibfahn]

+1 to having more knowledgeable non-core people helping out with docs, @davidgatti if you'd be interested in contributing to a User guide on streams (as discussed in #25) that'd be great.