Jimmy Wärting

We also want to test real ESM in the browser

sounds good so far. There is also the possibility of using import maps for node_modules

- IE only makes up for 0.25% of the global marketshare according to [statcounter](https://gs.statcounter.com/browser-market-share) - filtering on [desktop only](https://gs.statcounter.com/browser-market-share/desktop/worldwide) don't even show IE in the list anymore - Even big...

Base64 is the worst... it takes up more memory (in size it's ~3x larger but javascript strings are also 16bits so it's ~6x more memory) And lets not mention how...

The `new Response(blob).body` [hack](https://github.com/w3c/FileAPI/issues/40) was the reason why we got `blob.arrayBuffer(), blob.text() & blob.stream()` You can use the same hack here ... `new Response(stream).blob()` Could you imagine what the fetch...

left a ball of roller coster and created more issues thats need to be fixed, don't sound like an easy task to write spec and working cross multiple threads and...

Still annoying. have blocked so many websites over the year. I have had that tweet bookmarked for such a long time now. sometimes I scroll down to the bottom of...

What if an http request supports byte range requests? Would be kind of nice to be able to "resume" a broken request 1. makes a normal request, sees that it...

like this proposal. this could make the conversion between node/whatwg stream easy if both have @@asyncIterator btw, An idea that poped up in whatwg/fetch#809 is if we maybe could have...

> I just realised that > ```js > ReadableStream.from([in]).pipeTo(cs.writable); > ``` That's not that far off from ```js new Response(in).body.pipeTo(cs.writable); ``` ...exacpt that Response can't handle iterators but it can...