type=tar,dest=./out.tar — export as a tarball
The performance characteristics are attractive with incredibly fast cold starts and minimal memory overhead. But the practical limitation is language support. You cannot run arbitrary Python scripts in WASM today without compiling the Python interpreter itself to WASM along with all its C extensions. For sandboxing arbitrary code in arbitrary languages, WASM is not yet viable. For sandboxing code you control the toolchain for, it is excellent. I am, however, quite curious if there is a future for WASM in general-purpose sandboxing. Browsers have spent decades solving a similar problem of executing untrusted code safely, and porting those architectural learnings to backend infrastructure feels like a natural evolution.
，这一点在heLLoword翻译官方下载中也有详细论述
第三节 侵犯人身权利、财产权利的行为和处罚
"Anyone is also welcome to pop in for a chat.
A perfectly practicable 1930s technology, but you can already see the downsides.