Really neat project and fantastic write-up. I always enjoy following the journeys of people who forge into the untamed lands of WASM.
I always find myself wishing I had a good excuse to use WASM for something, but never being able to find one, so it's exciting to see that you did! The fact is that JavaScript logic is rarely the bottleneck in web apps. And when it is, it's usually tangled up in UI rendering code that would be hard to tease out into WASM. You do bring up an interesting point, though, which I hadn't considered: WASM isn't just faster, it's smaller. That alone could make it useful in some cases where the speed may not be needed!
Thanks! On top of the size benefits, I love that I can finally use languages other than JavaScript on the frontend. I couldn't have done it in JS because I'd have to write a BloomFilter implementation in it (which I would not be capable of) or bundle an existing library, which would have increased code-size (hence, defeating the point of the project). Portability is the other big feature of wasm.
I always find myself wishing I had a good excuse to use WASM for something, but never being able to find one, so it's exciting to see that you did! The fact is that JavaScript logic is rarely the bottleneck in web apps. And when it is, it's usually tangled up in UI rendering code that would be hard to tease out into WASM. You do bring up an interesting point, though, which I hadn't considered: WASM isn't just faster, it's smaller. That alone could make it useful in some cases where the speed may not be needed!