Duplexer confusing example about stream-adventure HOT 8 CLOSED

the confusion here stems from the following:

• process.stdin: 📖 Readable stream
• process.stdout: 📝 Writable stream
• childProc.stdin: 📝 Writable stream
• childProc.stdout: 📖 Readable stream

for process you're inside the process to stdin is readable to you, for child process you're outside so that process's stdin is writable to you.

from stream-adventure.

+1 on this. The confusing element for me here isn't duplexer's argument order necessarily (which are explicitly mentioned in the instructions), but that child_process.stdin is a Writeable stream (as opposed to process.stdin, which is a Readable stream) and child_process.stdout which is likewise flipped from process.stdout. So I struggled for a while with

return duplexer(childProcess.stdout, childProcess.stdin);

Because I didn't realize that child_process flipped the stdin/stdout stream types (not because I didn't grok that the Writeable should come first).

At the very least perhaps a heads up to this little twist in child_process?

from stream-adventure.

I also found myself confused as to why

return duplexer(childProcess.stdout, childProcess.stdin);

didn't work.

from stream-adventure.

+1

from stream-adventure.

+1 The @Sequoia explanation must be in the documentation.

from stream-adventure.

Thank you @Sequoia for the explanation, I got confused as well. However, even the reference solution doesn't work due to a unit test failing

not ok 3 should be equal
  ---
    operator: equal
    expected:
      'ihrl\nibza\nipzjbpa\nillasl\nillasl\nihghhy\nivvw\nillw\nillw\nibza\nibn\
nilla\nifghuapul\nive'
    actual:
      'ihrl\nibza'
  ...

from stream-adventure.

Nice discussion, definitely worth having the explanation from @Sequoia in the exercise to be accessible to anyone going through the problem. Opened a PR to include these additions in the hints.

from stream-adventure.

Closing since changes was added in #196

from stream-adventure.