> Most Node code I encounter that uses “streams” gets something wrong

This is really true. I ported a Node project to Go for this reason, and the streams in Go were miles easier to reason about.