Adam Rice

I feel like we are in a golden age where we can add synchronous primitives to workers without the horrible hacks that are required on the main thread. I also...

I think if browsers can use the underlying OS facility to implement mmap, then the risk of deadlock will be minimised. A concern I have is that browsers will schedule...

> A lot of early worker demos used sync XHR, so I guess workers were invented with non-CPU bounding in mind. Of course, browsers may have optimised differently. Chrome still...

I decided to verify the checksums by default, and possibly add a "power user" option to turn them off. As you say, the data will most likely have already been...

@ericlaw1979 Thanks. We settled on using "deflate" to mean "zlib" for consistency with HTTP, and will add "deflate-raw" in future to support zip and other use cases where the header...

We used to have a test in Chromium that relied on fixed compressed output for a particular input, but the people who are trying to improve our gzip implementation complained,...

Based on my experience, I think a dependency on the actual byte output of a compression algorithm is rare, so the risk is low. I consider the benefit to browsers...

@annevk It's my understanding that Microsoft Edge doesn't use zlib. It has its own implementation of deflate (and gzip). As far as I know, once Edge moves to Chromium all...

An attraction of snappy from Chromium's point of view is that it is already compiled into the binary as part of leveldb. A cursory search indicates Firefox also appears to...

I had overlooked this point. I was only thinking about getting maximum compression, not minimising latency. I am thinking that adding an option to flush after each chunk might be...