> the only viable use cases were compute-heavy workloads like codecs and crypto, I tried using it for crypto, but WASM does not have instructions for crypto. S

> the only viable use cases were compute-heavy workloads like codecs and crypto, I tried using it for crypto, but WASM does not have instructions for crypto. So it basically falls back to be non-hw-accelerated. Tried to find out why and the explanation seems to be that it's not needed because JS has a `crypto` API which uses hw intrinsics.