Comment by jarjoura

3 months ago

I thought WASM was no_std since there's no built in allocator?

Regardless, not sure why a Rust engineer would choose this path. The whole point to writing a service in Rust is that you would trade 10x time build complexity and developer ovearhead for getting a service that can run in a low memory, low CPU VM. Seems like the wrong tools for the job.

1 comment

jarjoura

ashishb 3 months ago

> Seems like the wrong tools for the job.

Thanks for the confirmation. I was confused as well. I always thought that the real use of WASM is to run exotic native binaries in a browser, for example, running Tesseract (for OCR) in the browser.