Out of all of the slowdown in execution that occur throughout the program's lifetime, it appears that the LZSS Decompression is the worst. It's almost certainly because we are decompressing in JavaScript instead of some compiled language like C++!!!
Now there are probably some solutions, including web-assembly, or maybe altering our compression to use something native to the browser, maybe something like base64 url encoding. Not sure if that would actually compress it much or not though. It'd be weird to get that working, so perhaps web-assembly may be the way to go. It would be relatively simple to rewrite the decompressor at least in C++, but I've never used web-assembly before so that's the catch at the moment.
Out of all of the slowdown in execution that occur throughout the program's lifetime, it appears that the LZSS Decompression is the worst. It's almost certainly because we are decompressing in JavaScript instead of some compiled language like C++!!!
Now there are probably some solutions, including web-assembly, or maybe altering our compression to use something native to the browser, maybe something like base64 url encoding. Not sure if that would actually compress it much or not though. It'd be weird to get that working, so perhaps web-assembly may be the way to go. It would be relatively simple to rewrite the decompressor at least in C++, but I've never used web-assembly before so that's the catch at the moment.