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.
“变”的是策略、方法与重心。平台必须变得更“重”，投入真金白银铺设数字基础设施，输出成熟的运营方法论，研发普惠的前沿技术，甚至担当维护公平市场环境的“裁判员”。其利润的来源，也日益体现为提供这些庞大而复杂的“重服务”所应得的回报。
。51吃瓜对此有专业解读
В России ответили на имитирующие высадку на Украине учения НАТО18:04
Play video, "張又俠被查：中國軍方最高級別將領落馬 官媒批其「造成極大破壞」", 節目全長 2,00