Adam Rice

I haven't looked at what would be required in detail, but my first instinct is that allowing reading from a `SharedArrayBuffer` would be relatively safe, as we always end up...

I work on the team that maintains EventSource for Chrome. EventSource is not being actively developed. We feel resources are better spent in filling the gaps in the more generally-useful...

Chrome accidentally does nothing successfully. I think we should throw. My guess is that no-one is intentionally using the current behaviour.

On my computer `http://example≯ ` looks very similar to `http://example>/`, which is not great. But it's probably not a good enough reason to change the status quo.

Okay. If there are no conflicting opinions then @nidhijaju or I will write a PR to prohibit synchronous behaviour.

Sorry, no, it slipped off my radar. Some WPT would be great!

> Another issue: > ... > This logs true on Gecko/Blink but false on WebKit. Maybe it's more natural to be synchronous here as `getReader().read()` pulls synchronously, except I'm not...

I would hope that native code would use an abstraction layer on top of `poll`, `read` and `write` which would make it easier to adjust the semantics. That's what Chromium's...

My initial assessment based on reading the proposal is that there is no impact on default streams, only byte streams. As far as I can tell, because we detach the...

I hadn't thought of that. I agree that developers will expect to get a resizable buffer back.