ML for resource-intensive apps. Client-side word vectorization would be a nice-to-have -- early classificatiton and sentiment analysis happening client-side ope

ML for resource-intensive apps. Client-side word vectorization would be a nice-to-have -- early classificatiton and sentiment analysis happening client-side opens up a ton of use cases. What I'm more excited for, is it also lets you write highly-optimized apps which would use less power, and possibly be served in smaller filesizes. This is great for mobile devices. e.g. managing and comparing 128-bit uints is a big headache in JS, so you rarely see UUIDs handled as anything but strings. There are a few optimizations around that, but ultimately it's going to be a lot easier on memory and run faster matching if you can store it directly as 16-bytes. Trivial in rust compiled to wasm, but not worth your time in JS. There are also still a lot of programs being compiled to windows/osx/linux target binaries, that could run just as well in a browser with wasm. It's easier to picture what you _don't_ run in browser now as a possibility, instead of simply imagining how the current web will look in wasm.