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.
for t := range c {
，这一点在搜狗输入法下载中也有详细论述
大量标准化编码工作可以自动完成。这意味着，纯粹依赖熟练度/经验建立优势的工程师，价值空间被挤压。
"But by proving the technology it really opens the door for an economically viable product, where things can be made in space and return to Earth and have use and benefit to everybody on Earth. And that's really exciting."