reading through whatwg @streamsstandard to update myself on its latest state — I have to say, I haven't seen anything disagreeable!
-
-
Replying to @isntitvacant
the ReadableStreamReader may seem Java-ish, but consider that by exposing `read` directly, users can stick their hands in the engine
2 replies 0 retweets 1 like -
Replying to @isntitvacant
put another way, Node streams expose an API that is half private and half public, and which half is which depends on how the stream is used
1 reply 0 retweets 3 likes -
Replying to @isntitvacant
@isntitvacant the new streams api has changed that, right?1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts streams2+ doesn't address the problem. If one has piped, one shouldn't call .read, .write, or .end, or emit certain events.1 reply 0 retweets 0 likes -
Replying to @isntitvacant
@yoshuawuyts (but if you're talking the WHATWG ReadableStreamReader + locking a ReadableStream for reading, yep! — that solves the problem)1 reply 0 retweets 0 likes
@isntitvacant no no, I was talking streams 2+. Thanks for clarifying ^__^
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.