Joshua Melville

Required before #847 can be implemented.

Also of note is that this would impact the `writeStream` filesystem method that we currently use to manage memory use. This method is called by `extractZipFile` to write the contents...

> Failing that, maybe we need to rethink how assets are transferred? Another option here is stronger support for remote URL assets, and/or embedding things like the youtube video player....

Some more research on this issue: - zip.js is essentially abandoned, and jszip is irregularly maintained and using pretty old code. - https://github.com/transcend-io/conflux looks like a promising alternative - a...

Further options is native compression/decompression which may have already landed in chrome: https://github.com/WICG/compression/blob/master/explainer.md (not yet landed in safari) Web assembly: https://github.com/drbh/wasm-flate and https://github.com/nika-begiashvili/libarchivejs

@keean - thanks for weighing in on this! I really appreciate your input. The issue we are trying to address here is both memory use (which as you say can...

@keean - Thanks again for providing your insight into this issue. Very much appreciated. It sounds like your approach will definitely work for us.

This may also impact large image/video assets. For example, the looped video with sound in the development protocol takes several seconds to load, even on fast devices.

Does anybody have any thoughts on a technical implementation for this?

Would the streaming method resolve the issues we currently see with a delay when initially showing a large asset, do you think?