3 ms·
> It’s a technique that used to be popular and then died out as networks proliferated—you could no longer be sure that your machine code did the right parse on
by immibis 5y ago
> It’s a technique that used to be popular and then died out as networks proliferated—you could no longer be sure that your machine code did the right parse on someone else's architecture.
This will be the case with WASM extensions. You won't be sure what's available in someone else's WASM environment.
The only reason it's not the case with WASM on the web today is because it's so simple, and any differences are dealt with in the JavaScript layer.
> Your container crashes and we coredump to an S3 bucket. You know what’s better than downloading gigabytes of coredump? If S3 can just let you spin up a container or run a WASM program on the storage node itself.
S3 literally has this feature, and it doesn't even have to be WASM. It's called "S3 Object Lambda". It's quite new, so you're forgiven for not knowing about it.
Downloading from S3 is quick and free if it's within the same region, so you don't actually need this anyway.